galtzo-floss / turbo_tests2 / 37838766239

94%

push

github

🐛 Disable TruffleRuby 22.3 CI, which deadlocked and blocked release v3.2.14

The TruffleRuby 22.3 job hung on the parallel worker runner twice:

  37628565052  6h2m16s  cancelled
  37804186826  ~56m     cancelled during this release

The hung run's log shows "4 processes for 13 specs" at 15:56:15 and then
no further output until GitHub's cleanup terminated orphan ruby PIDs
2355/2415/2431 at 16:49:18 -- the worker pool deadlocked rather than
progressing.

The job is experimental with continue-on-error, so a failure never blocks
a release. A hang never completes, so the release CI monitor waited on it
and publishing v3.2.14 never ran. The workflow carried no timeout-minutes,
leaving GitHub's 6-hour ceiling as the only backstop.

This is the same defect already fixed for TruffleRuby 23.0 in 143cb63,
which forced serial workers via TURBO_TESTS2_MAX_PROCESSES and added a
30-minute cap. That fix was applied to the generated workflow only, not to
the kettle-jem template, so 22.3 never received it.

TruffleRuby 22.3 is EOL and targets Ruby 3.0 compatibility, which remains
covered by TruffleRuby 23.0 (serial workers) plus the maintained MRI and
JRuby runtimes, so the job is dropped rather than serialized.

Deleting the generated workflow alone would not survive the next template
run, so .structuredmerge/kettle-jem.yml records strategy: keep_destination
for it. That strategy means "no merge, no creation", verified here by a
scoped kettle-jem install --only on this path, which reported 0 changed
files and did not recreate the workflow.

The shared ruby-3-0 appraisal is still used by ruby-3.0.yml and
truffleruby-23.0.yml, so Appraisals is unchanged.

Signed-off-by: Peter H. Boling <peter.boling@gmail.com>

256 of 298 branches covered (85.91%)

Branch coverage included in aggregate %.

947 of 977 relevant lines covered (96.93%)

16.89 hits per line