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

stillwater-sc / universal / 38995555605
89%
master: 84%

Build:
Build:
LAST BUILD BRANCH: main
DEFAULT BRANCH: master
Ran 17 Oct 2026 03:03AM UTC
Jobs 1
Files 724
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

17 Oct 2026 02:35AM UTC coverage: 86.68% (+0.01%) from 86.666%
38995555605

push

github

web-flow
ci: bring the ready-PR cycle back to ~20 minutes (#1706)

* ci: bring the ready-PR cycle back to ~20 minutes

A ready PR waited on Coverage (52 min), UBSan (46 min) and the slowest
cross build (32 min). Nothing failed in one step; four costs had grown.

1. Coverage and Sanitizers had no compile cache and under-used the runner.
   Each run rebuilt the whole CI tree in Debug (13-24 min). Coverage ran
   its ~1000 tests serially (36 min); Sanitizers ran at -j 2, sized for
   the old 2-vCPU / 7 GB runner. Now each job has a ccache, saved on main,
   and tests run at -j $(nproc). The runner has 4 vCPUs and 16 GB; each job
   prints this so the assumption is checked. Sanitizers now also build
   (without testing) on a push to main, so their cache stays warm. The
   UBSan per-test timeout goes from 300s to 600s for the shared machine.

2. The slowest jobs never saved a cache. ccache-action saves a new
   timestamped generation on every main push. Until Prune ran, the old and
   new generations coexisted, and that doubling took the cache past its
   budget mid-run. The jobs that finished early saved; the late ones
   (POWER, RISC-V, macOS x64, full-tier Linux) failed with "Unable to
   reserve cache", so they stayed cold (0% hits), so they stayed slow. Each
   job now deletes the generation it restored before its post step saves
   (tools/scripts/ci-drop-ccache-generation.sh), which keeps the footprint
   flat. Prune remains as the backstop.

3. The full-tier Linux jobs restored the wrong cache. ccache-action
   restores by key prefix and takes the newest match, so "linux-x64-gcc"
   matched linux-x64-gcc-fast. Those jobs restored the fast tier's 474
   objects of their 912 (25-50% hits). They are now linux-x64-{gcc,clang}-full.

4. Every compile carried -DGIT_COMMIT_HASH and -DGIT_BRANCH. No source
   reads them, but they change on every commit, which costs ccache its
   direct-mode hits. They stay in the version string.

Also:
- cmake builds use --parallel ... (continued)

49432 of 57028 relevant lines covered (86.68%)

10435014.6 hits per line

Jobs
ID Job ID Ran Files Coverage
1 38995555605.1 17 Oct 2026 03:03AM UTC 724
86.68
GitHub Action Run
Source Files on build 38995555605
  • Tree
  • List 724
  • Changed 1
  • Source Changed 0
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #38995555605
  • 8fc25f03 on github
  • Prev Build on main (#38992615351)
  • Next Build on main (#39047295777)
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