ponder-lab / Hybridize-Functions-Refactoring / #3397
89%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 45
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: 87.982%. Remained the same
#3397

push

github

web-flow 
Check functions in parallel in the drivers, and judge a run by its exit code (#1054)

* Check functions in parallel in the drivers, and judge a run by its exit code

Since #1051 and #1052, a parallel run's results match a serial run's, so the IDE launch and the reinfer harness now set processFunctionsInParallel. The evaluator's own default stays off, like every other knob, and each results row records the mode. The headless script's header no longer calls the mode nondeterministic.

The reinfer harness now takes the launcher's exit code as its witness instead of the completion line. The evaluator logs that line at INFO when every project succeeds, so a run logging at WARNING or above leaves it out, and the harness would count every successful run as failed. Since #1053, the exit code is 0 exactly when every project succeeds. The log is still read to say why a run failed.

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

* Scope the parallel-mode comment, and name a skip whose reason wasn't logged

The script's header said a parallel run's results match a serial run's. Only the state shared in this tool is synchronized; not all of PyDev's module caches are, so the comment now says that instead.

A run that exits 6 without its completion line in the log, as at log level ERROR, now reads "skipped (reason not logged)" rather than as an unexplained stop.

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

* Say what bounds the PyDev race in parallel mode

Every call this tool makes into PyDev's module caches, its definition and class-hierarchy lookups, holds the lock #1052 added; its other PyDev calls don't reach those caches. PyDev's own background analysis would run outside the lock, in serial mode as in parallel mode, but it has been observed idle during evaluation. The script's header now says tha... (continued)

4810 of 5467 relevant lines covered (87.98%)

0.88 hits per line

Jobs
ID Job ID Ran Files Coverage
1 #3397.1 45
87.98
Source Files on build #3397