Skip to content

Keep Core tests within CI limits and export reviewed Alpine receipts - #17

Draft
LIghtJUNction wants to merge 9 commits into
mainfrom
fix/core-ci-rust-targets
Draft

LIghtJUNction wants to merge 9 commits into
mainfrom
fix/core-ci-rust-targets

Conversation

@LIghtJUNction

@LIghtJUNction LIghtJUNction commented Nov 22, 2026 •

Copy link
Copy Markdown
Member

The microkernel runner hit its 150-minute job limit in two pull-request revisions while real database tests were still progressing. On the final #15 merge-test tree, the main CI job passed all 1,935 active library tests and 43 payment cases, then ran out of time during a real payment process test. The identity job ran the same tree through all stages successfully. The earlier revision also timed out on both runners. Final primary job · Successful identity job · Earlier primary job

Automatic CI and identity checks now give integration targets and the other Cargo targets separate runners. Each runner keeps the 150-minute limit, runs one Rust test thread, and uses its own pinned PostgreSQL service. Both matrix results are required. The original protocol job runs the Go, store, event and native RPC checks. The real payment verifier and service boundary checks also run on the integration runner. The additional runner preserves its compiler, source and test evidence under a separate artifact name. Manual qualification keeps its existing all-target invocation.

Local Cargo compilation on parent a9fab47 produced 162 test executables. The four library, binary and example targets and 158 integration targets were disjoint, and their union matched all 162 original executable paths. The unit selection also covers benchmarks as they are added. All 21 workflow topology tests and actionlint 1.7.12 passed. The unchanged component gate returned failure for failed, cancelled and skipped kernel results.

Updating the topology test triggers the native Linux packaging workflow. Its previous upload path recursively included the evidence directory. The first packaging run was stopped before upload and retained zero artifacts. This branch now includes the original reviewed Alpine fixture and receipt export from #13 at its existing commit 7d0d33b. The service user checks the installed executable, the real plugin is loaded with networking disabled, and the runner exports only the reviewed probe/package JSON and explicit package/acceptance files. Fixture logs stay private. Both receipt tests passed locally. A topology regression rejects the original broad upload on main and passes with the reviewed path list and private process transcript. The amd64 and arm64 jobs exercise the real packages.

The Alpine smoke probe reaches a healthy installed service, then fails when the container-root observer reads the other UID's procfs executable link.
Run that exact read as the existing service UID and GID with no supplementary groups. Keep the executable-path assertion, timeout, error propagation and subsequent native catalogue checks.

(cherry picked from commit 36f3de2)
Use the Alpine readlink applet under the service account and omit its output delimiter. Comparing the raw bytes preserves filename whitespace, including trailing spaces, when verifying the running executable.
Keep the native probe report and consumer output in a private container directory. Write only confirmed receipt fields into runner-owned staging files after the real probe passes. Upload the paths returned by the package builder and the named acceptance records.
@LIghtJUNction LIghtJUNction changed the title Run serial Core tests on isolated CI runners within the existing timeout Keep Core tests within CI limits and export reviewed Alpine receipts Nov 22, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant