Skip to content

Ruby: use dual graph for common module ancestor check #30975

Ruby: use dual graph for common module ancestor check

Ruby: use dual graph for common module ancestor check #30975

Triggered via pull request March 12, 2026 12:27
Status Success
Total duration 2m 42s
Artifacts 4
Generate framework coverage artifacts
2m 38s
Generate framework coverage artifacts
Fit to window
Zoom out
Zoom in

Annotations

1 warning
Generate framework coverage artifacts
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
comparison
142 Bytes
sha256:064d42b21a8ea25d23d4e692188abbf75909369459656e3c7924771451720aad
csv-framework-coverage-base
13.7 KB
sha256:52480944c203cd1718553d263db56d08e0fcd9de63454927532f232ffae66891
csv-framework-coverage-merge
13.7 KB
sha256:aefc1ecbeb31c0a77fabc64e96c9d9c0e912739983740b47d90fa781313f5487
pr
126 Bytes
sha256:cec3330db90a2055e68a73d0bb4e8ec4dae2d532415fedb1c2ebdfa213b7b253