• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

galtzo-floss / turbo_tests2 / 38020852928
94%

Build:
DEFAULT BRANCH: main
Ran 10 Oct 2026 03:33AM UTC
Jobs 1
Files 11
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

10 Oct 2026 03:28AM UTC coverage: 94.353%. Remained the same
38020852928

push

github

pboling
📝 Correct engine and platform support tiers

The tier table claimed coverage no workflow provides. Three rows and one
paragraph were false:

  TruffleRuby 22.3   claimed Parallel support, CLI and multi-process
                     groups skipped for Ruby compat 3.0
  TruffleRuby 23.0   claimed Single-worker support, CI caps workers at one
  TruffleRuby head   claimed Parallel support, allowed to fail

No workflow runs any of them. CI covers truffleruby 23.1, 24.2, 25.0,
33.0 and current (34.0) only. heads.yml runs ruby-head and jruby-head,
with no truffleruby-head job. dep-heads.yml runs the released truffleruby
engine against head-of-branch dependencies, which is not a head engine
build, so it does not license a "TruffleRuby head" row either.

The rspec-pending_for explanation was also false: rspec-pending_for is
neither a dependency nor referenced by any spec, so the exclusions it
describes do not exist.

The badge rows and workflow link definitions for 22.3 and 23.0 were
already removed by templating in 3ed2581, which left the prose table
describing CI that no longer runs.

The asymmetry is explained by how templating treats each part. The badges
come from KJ tokens, so regenerating the README rebuilt them from current
facts and dropped the retired versions. The tier table is destination
prose living inside "## Synopsis", and synopsis is one of
README_DEFAULT_PRESERVE_SECTIONS, which the destination config does not
override (preserve_sections is commented out, so defaults apply).
Templating therefore carries it forward verbatim instead of regenerating
it - which is the point of preservation, and why the stale rows survived
every template run while the badges did not.

So the table is template-managed in the sense that templating owns its
placement and deliberately preserves its content; it is simply not
token-generated. Correcting stale preserved content means editing the
destination README, which is what this commit does. No token produces it:
"Ru... (continued)

256 of 298 branches covered (85.91%)

Branch coverage included in aggregate %.

947 of 977 relevant lines covered (96.93%)

15.79 hits per line

Jobs
ID Job ID Ran Files Coverage
1 38020852928.1 10 Oct 2026 03:33AM UTC 11
94.35
GitHub Action Run
Source Files on build 38020852928
  • Tree
  • List 11
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #38020852928
  • 1c8af655 on github
  • Prev Build on main (#38011229525)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc