kayg/infraternal-v0
Archived
Watch
1
0
Fork
You've already forked infraternal-v0
 0
Code Issues 92 Pull requests Projects Releases Packages Wiki Activity Actions

Serialize full verification gates before compilation #53

Open
opened 2026-10-04 17:38:30 +00:00 by kayg · 0 comments
kayg commented 2026-10-04 17:38:30 +00:00
Owner
Copy link

Problem and evidence

The architecture review's scripts/verify fast run took 864.038 seconds on an eight-CPU VM (load5 13.09 → 10.74); the report explicitly does not claim a merge duration. That already uses 96% of PLAN's 900-second merge target before release build and real-service smokes. scripts/verify only warns when load5 exceeds the CPU count (`scripts/verify:858-869)); it does not serialize ordinary full gates. PLAN step 7 says not to run parallel full gates.

Recommendation

Have the existing orchestration reserve one full-gate slot before any compilation starts. Record queue wait separately from gate time and host load. Keep scripts/verify as the only gate entry point and retain all stages.

Payoff and estimate

Prevents simultaneous full gates from creating avoidable retries and makes the measured gate time interpretable. Estimate: 0.5–1 engineering day. Completion evidence: two queued jobs show only one full gate running, and each retains its normal coverage/output.

Priority: Now (≤1 day).

2026-10-04 owner decisions: Matches the performance-first gate rule and the requirement to keep code/tests as the spec. No new gate entry point is needed.

Report: arch-review report
Source: arch-review 2026-10-04

## Problem and evidence The architecture review's `scripts/verify fast` run took 864.038 seconds on an eight-CPU VM (load5 13.09 → 10.74); the report explicitly does not claim a merge duration. That already uses 96% of PLAN's 900-second merge target before release build and real-service smokes. `scripts/verify` only warns when load5 exceeds the CPU count (`scripts/verify:858-869)); it does not serialize ordinary full gates. PLAN step 7 says not to run parallel full gates. ## Recommendation Have the existing orchestration reserve one full-gate slot before any compilation starts. Record queue wait separately from gate time and host load. Keep `scripts/verify` as the only gate entry point and retain all stages. ## Payoff and estimate Prevents simultaneous full gates from creating avoidable retries and makes the measured gate time interpretable. Estimate: 0.5–1 engineering day. Completion evidence: two queued jobs show only one full gate running, and each retains its normal coverage/output. **Priority:** Now (≤1 day). **2026-10-04 owner decisions:** Matches the performance-first gate rule and the requirement to keep code/tests as the spec. No new gate entry point is needed. **Report:** [arch-review report](/mnt/hdd/infraternal/jobs/arch-review/report.md) **Source: arch-review 2026-10-04**
Commenting is not possible because the repository is archived.
No Branch/Tag specified
Branches Tags
main
dev
perf-gates
provider-docker-podman
fix-networkidle
fix-apierror-panics
fix-revoke-panic
wal-race
fix-private-storage
provider-runtime
plugin-design
server-channels
scope-v01
deploy-git-fix
sec-hardening
gates-tiering
sidebar-sync
multi-tab
cli-eof
podman-flake
ssh-reattach
agent-tunnel
process-boundary
shadcn
stream-params
cli-ssh
ssh-product
container-live
flaky-tests
s1-e2e
ssh-test-isolation
cli-stream
research-lxc
container-live-agent
ui-apis
grant-shrink
deploy-o2
ui-redesign
migration-fix
cli
stream
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
kayg/infraternal-v0#53
No description provided.