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

archetech / archon / 32587571746
87%

Build:
DEFAULT BRANCH: main
Ran 22 Aug 2026 05:27PM UTC
Jobs 1
Files 91
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

22 Aug 2026 05:23PM UTC coverage: 93.894%. Remained the same
32587571746

push

github

web-flow
fix(ci): Seed native prebuilds in the three jobs that were missed (#926)

* fix(ci): Seed native prebuilds in the three jobs that were missed

Closes #913.

Not a new problem: #879 already removed the network from this path by
seeding ./prebuilds before the image build, since sqlite3's install script
is `prebuild-install -r napi || node-gyp rebuild` and the slim base images
have no toolchain for the fallback to use. Its own commit message says it
covered "the three workflows that now run the prefetch" -- but six jobs
build images, and three were left out:

- python-sdk-tests.yml, which is where #913's failure was observed
- docker-build-test.yml :: build_test_images, which builds through
  start-node-ci, so the build is invisible to a grep of the workflow
- docker-build-test.yml :: gatekeeper_parity, `up -d --build`

All three are PR-triggered, which is why the symptom was a spurious red
check on any PR.

The issue asked to check option 3 first -- drop sqlite3 if the images do
not use it. They do: services/keymaster/server/src/keymaster-api.ts:12
imports WalletSQLite statically and instantiates it at :256, and the
gatekeeper imports it dynamically. It is a supported backend, so removing
it was never available.

The guard checks per JOB, not per file: docker-build-test.yml has two
image-building jobs and covering one would look right from outside, which
is close to how the original miss happened. It also checks that a
Dockerfile copying prebuilds/ points prebuild-install at it, since one
without the other silently falls back to the network.

Mutation-tested three ways -- reverting python-sdk-tests, dropping the
prefetch from only the second job, and removing a Dockerfile's env var --
each turns it red. The prefetch script was run rather than assumed to
work: all four tarballs fetched.

tests/ci uses `yaml` rather than js-yaml because it ships its own types,
so this declares one dependency instead of two. Both were undeclared
transitives; #924's review ... (continued)

3806 of 4293 branches covered (88.66%)

Branch coverage included in aggregate %.

8465 of 8776 relevant lines covered (96.46%)

689.48 hits per line

Jobs
ID Job ID Ran Files Coverage
1 32587571746.1 22 Aug 2026 05:27PM UTC 182
94.92
GitHub Action Run
Source Files on build 32587571746
  • Tree
  • List 91
  • Changed 77
  • Source Changed 0
  • Coverage Changed 77
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #32587571746
  • ff981db3 on github
  • Prev Build on main (#32585001255)
  • Next Build on main (#32594720021)
  • 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