You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 55cc25a
Browse filesBrowse the repository at this point in the historyBrowse files
Brings in the configure-time check that a test carrying the fast label must be listed in PINEFORGE_PR_FAST_TESTS. The merge applied without conflicts and changes no file of the cache work.
Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
Copy file name to clipboardExpand all lines: tests/cr150.d/README.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,6 @@
1
1
Each CR-150 lane has one file named `<lane>.cmake` holding that lane's `list(APPEND TEST_SOURCES ...)` and `pineforge_add_unit_test(...)` lines in the same one-line-per-item form; files are included in sorted name order by the shared include loop at the end of the plain registrations in `tests/CMakeLists.txt`, and a lane must never edit another lane's file.
2
2
`set_tests_properties(...)` may name only tests registered by the same lane's file or fence; tests from the main file or another lane are not owned by that lane. Only the property keys `LABELS`, `SKIP_RETURN_CODE`, `RUN_SERIAL`, and `DEPENDS` are allowed (`TIMEOUT` is rejected: this repository declares no time limits, owner rule #827); `set_target_properties(...)` is forbidden. In lane files and fences, `SKIP_RETURN_CODE` must be the literal `77`, the receipt-gated skip sentinel tracked by `scripts/check_abi_receipt_skips.py`; every other skip return code is rejected.
3
+
A test may carry the label `fast` only through `PINEFORGE_PR_FAST_TESTS`, and configure fails otherwise.
3
4
4
5
After the include loop, only zero or more `# --- CR-150 <lane> begin ---` / `# --- CR-150 <lane> end ---` blocks may appear before the canonical fast-row registration block; each block must be matched, nonnested, unique, and named with the exact stem of an existing `tests/cr150.d/<lane>.cmake` file.
5
6
Lane files and appended blocks go above the fast-row registration block, which must stay the last CMake code in `tests/CMakeLists.txt`. The sole unfenced exception is that terminal PR-fast validation block for `PINEFORGE_PR_FAST_TESTS` and its `pineforge_pr_smoke` target: no lane file or fence may follow it.
0 commit comments