didericis/bot-bottle
1
0
Fork 0
Code Issues 36 Pull Requests 5 Actions Packages Releases Wiki Activity

PRD: CI artifact-based coverage and local Firecracker candidate flow #447

Merged
didericis merged 5 commits from ci-artifact-coverage into main 2026-07-21 12:59:33 -04:00
Conversation 0 Commits 5 Files Changed 6
+360 -118
didericis-claude commented 2026-07-21 00:05:16 -04:00
Collaborator
Copy Link
Copy Source

Closes #446.

PRD

Summary

  • Each test job (unit, integration-docker, integration-firecracker) runs once under coverage and uploads a small .coverage.* artifact.
  • The coverage job combines them on ubuntu-latest — no test reruns, no KVM dependency on that job.
  • The infra candidate is built directly on the KVM runner in integration-firecracker, eliminating the stage-firecracker-inputs and build-infra jobs and their ~70 s upload + ~83 s combined download overhead.
  • PRs incur no rootfs artifact transfer (~194 MB saved per PR run).
  • Main-branch pushes upload the tested rootfs and matching dropbear so publish-infra publishes the byte-identical artifact that passed integration tests.
  • relative_files = True added to .coveragerc so .coverage.* files from different runners combine without a [paths] remapping section.
  • scripts/coverage.sh aggregate [critical] mode added; existing run mode preserved for local dev.
Closes #446. [PRD](https://gitea.dideric.is/didericis/bot-bottle/src/commit/5940b75bb72d2de30e7bb55775957fa18453454a/docs/prds/prd-new-ci-artifact-coverage.md) ## Summary - Each test job (`unit`, `integration-docker`, `integration-firecracker`) runs once under coverage and uploads a small `.coverage.*` artifact. - The `coverage` job combines them on `ubuntu-latest` — no test reruns, no KVM dependency on that job. - The infra candidate is built directly on the KVM runner in `integration-firecracker`, eliminating the `stage-firecracker-inputs` and `build-infra` jobs and their ~70 s upload + ~83 s combined download overhead. - PRs incur no rootfs artifact transfer (~194 MB saved per PR run). - Main-branch pushes upload the tested rootfs and matching dropbear so `publish-infra` publishes the byte-identical artifact that passed integration tests. - `relative_files = True` added to `.coveragerc` so `.coverage.*` files from different runners combine without a `[paths]` remapping section. - `scripts/coverage.sh aggregate [critical]` mode added; existing run mode preserved for local dev.
didericis added 4 commits 2026-07-21 12:43:34 -04:00
ci: artifact-based coverage and local Firecracker candidate flow 3fba385513 
Each test job now runs once under coverage and uploads a small .coverage.*
artifact. The coverage job combines them on ubuntu-latest — no test reruns,
no KVM dependency. The infra candidate is built directly on the KVM runner,
eliminating the build-infra job and the ~70 s upload + ~83 s combined
download. For PRs, no rootfs artifact is transferred at all. Main-branch
pushes upload the tested rootfs and matching dropbear so publish-infra
publishes the byte-identical artifact. relative_files = True in .coveragerc
lets coverage files from different runners combine without path remapping.

Closes #446
fix(ci): use absolute github.workspace paths for coverage artifact upload/download 8ce8a8cc62 
The delphi-ci runner resolves relative paths in upload-artifact and
download-artifact from a different CWD than run: shell steps, so
'.coverage.unit' etc. were never found. Using ${{ github.workspace }}
gives an absolute path that does not depend on the JS action's CWD.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
fix(ci): use COVERAGE_FILE env var for reliable artifact paths; add --reuse-published to infra build 0c91c75a05 
coverage run's --data-file flag can be overridden or ignored in some
runner environments (Nix Python, older act-based runners). Switching to
the COVERAGE_FILE env var with an absolute ${{ github.workspace }} path
ensures coverage.py writes to a known location in every runner context,
so upload-artifact can find the file.

Also adds --reuse-published to the infra build step: if the artifact for
this content hash already exists in the registry, download it instead of
running the full docker build → mke2fs → gzip pipeline.
fix(ci): stage coverage data under non-dot names so upload-artifact uploads them
tracker-policy-pr / check-pr (pull_request) Successful in 12s
Details
test / integration-docker (pull_request) Successful in 18s
Details
lint / lint (push) Successful in 52s
Details
test / unit (pull_request) Successful in 1m59s
Details
test / integration-firecracker (pull_request) Successful in 3m23s
Details
test / coverage (pull_request) Failing after 40s
Details
test / publish-infra (pull_request) Has been skipped
Details
26002b75ca 
upload-artifact@v3's glob silently skips hidden files, so uploading a
bare `.coverage.unit` logged "No files were found. No artifacts will be
uploaded" and registered nothing — the coverage job's download then 404'd
("List Artifacts failed: 404"). The coverage report step read the same
file fine, confirming it existed; only the leading dot broke the upload.
The old pipeline's cross-job artifacts (infra-candidate/, firecracker-
inputs) worked precisely because they were non-dotfiles.

Each test job now copies its .coverage.<suffix> to a non-dot
coverage-<suffix>.dat before upload (the cp also fails loudly if coverage
never wrote the file), and the coverage job renames them back to
.coverage.* before `coverage combine`.
didericis force-pushed ci-artifact-coverage from 41e01d745a to 26002b75ca 2026-07-21 12:43:34 -04:00 Compare
didericis added 1 commit 2026-07-21 12:55:14 -04:00
test(firecracker): cover published artifact reuse
tracker-policy-pr / check-pr (pull_request) Successful in 9s
Details
test / integration-docker (pull_request) Successful in 16s
Details
test / unit (pull_request) Successful in 1m37s
Details
test / integration-firecracker (pull_request) Successful in 3m30s
Details
test / coverage (pull_request) Successful in 15s
Details
test / publish-infra (pull_request) Has been skipped
Details
prd-number / assign-numbers (push) Failing after 23s
Details
test / integration-docker (push) Successful in 15s
Details
lint / lint (push) Successful in 58s
Details
test / unit (push) Successful in 38s
Details
Update Quality Badges / update-badges (push) Failing after 1m40s
Details
test / integration-firecracker (push) Successful in 5m9s
Details
test / coverage (push) Successful in 44s
Details
test / publish-infra (push) Successful in 2m7s
Details
8348714e3e
didericis merged commit 8348714e3e into main 2026-07-21 12:59:33 -04:00
didericis deleted branch ci-artifact-coverage 2026-07-21 12:59:38 -04:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
Status/Needs Triage
Awaiting initial classification
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
didericis-claude (didericis (claude)) didericis-codex (didericis (codex)) didericis-gemma (gemma) didericis
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: didericis/bot-bottle#447
Delete Branch "ci-artifact-coverage"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?