ponder-lab / Hybridize-Functions-Refactoring / #3579
90%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 47
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 88.594%. Remained the same
#3579

push

github

web-flow 
Print the resolved engine build in CI (#1116)

* Print the resolved engine build in CI

The Maven builds run with `-q`, so the log never names the engine
snapshot that resolved. Add an `if: always()` step after the tests that
prints, to the log and the step summary, the file name and SHA-1 of every
resolved `com.ibm.wala.cast.python.ml` jar (and of the other WALA bundles
the target wraps), the snapshot `<timestamp>`/`<buildNumber>` from any
`maven-metadata*.xml`, and the ML version `hybridize.target` pins. A
missing directory prints "not resolved" rather than failing the job.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NTnpjPjJj2aZy1ZkUD1eAn

* Print only the engine jar the build resolved

On a bump branch, the Maven cache accumulates several timestamped
snapshot jars under one version directory, and listing them all invites
comparing the wrong SHA-1 against the registry. For the version
`hybridize.target` pins, read `<timestamp>` and `<buildNumber>` from the
repository metadata `-U` refreshed and mark the jar they name as
resolved; for a release, mark the jar at exactly the pinned version.
Print only that jar with its SHA-1, plus a count of the other cached ML
jars, leaving Tycho's `bnd-*` copies out of both. Say so explicitly when
the metadata is missing or no cached jar matches.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NTnpjPjJj2aZy1ZkUD1eAn

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

5212 of 5883 relevant lines covered (88.59%)

0.89 hits per line

Jobs
ID Job ID Ran Files Coverage
1 #3579.1 47
88.59
Source Files on build #3579