Repository navigation
qa_verify: its gates run cargo against the root facade (0 tests); every section exits 1 #5026
Description
crates/aprender-core/examples/qa_verify.rs runs its gates as child cargo processes (run_cargo, line 121) with no working directory set, so they run wherever the example was started. Started from the checkout root, as examples-nightly starts it, cargo selects the root facade package, whose src/lib.rs is a re-export with no tests.
Measured on 73f3426, in a debug build with stdout and stdin not a terminal, after building the example alone in an empty build directory. The receipt is evidence/examples-nightly-4756/qa_verify-sections.txt on #4756's branch.
| run | secs | rc | gates |
|---|---|---|---|
--section 2, first |
325 | 1 | P040–P043 all FAIL, "Tests failed" |
--section 2, again, nested builds present |
81 | 1 | P040–P043 all FAIL |
--section 1, run third |
283 | 1 | P034 Unit Tests Pass FAIL; P035 Test Count > 700 FAIL, "Only 0 tests"; P036 Examples Build PASS; P037 Clippy Clean FAIL, "4 warnings"; P038 Format Check PASS; P039 Docs Build FAIL |
Not measured: why each gate failed. qa_verify discards the nested cargo output, and run_cargo ignores its timeout argument (_timeout_secs).
History: on main, examples-nightly ran qa_verify bare and the row was a timeout ("run killed after 180s", CI run 37169058144). From #4756, a bare run in a debug build or with no terminal prints its usage (needs-args). --all and --section N still run the gates from any build. This ticket is the gates themselves, outside #4756's 36 rows.
Done when: on a main whose CI is green, cargo run --example qa_verify -p aprender-core -- --section 1 and -- --section 2 exit 0, each gate measures the package it names (not the facade), and a failing gate prints why.
Refs #4756
🤖 Generated with Claude Code
Activity
evidence(#4756): answer review round 7 — why each bare run is needs-a…
fix(examples): examples-nightly 36 rows to pass or a skip class, fail…
noahgift commentedon Oct 14, 2026
Folded into #2876 as a checklist row (TRIAGE-100, 2026-10-14): the open-ticket cap is 100, so this ticket is now tracked on that master and closed as not planned. Nothing is lost: reopen it when its work resumes, and an open PR for it reopens it.
Agent: aprender-clerk