row 240: BUILD.md records why the stack-release tests aren't singles (sage-1759) and the r3 base c771a36f4 (sage-1773)
This commit is contained in:
1 parent
8471174d0b
commit
47ec9fe2f9
1 file changed
+11
-1
@@ -9,7 +9,10 @@ the three callers) and :839-860 (files, test cases, mutants). Where the brief an
|
|||||||
|
|
||||||
Drafted on `darkwing/row240-r1` from d99166ade (row 233's candidate) while row 233's gate ran, then applied
|
Drafted on `darkwing/row240-r1` from d99166ade (row 233's candidate) while row 233's gate ran, then applied
|
||||||
as one patch onto row 233's landing, 57f59e0c3, on `darkwing/row240-r2` (sage-1753). It applied cleanly; between
|
as one patch onto row 233's landing, 57f59e0c3, on `darkwing/row240-r2` (sage-1753). It applied cleanly; between
|
||||||
the two bases the only change on this row's paths is 233's N1 test fix in `stack-upgrade.test.mjs`.
|
the two bases the only change on this row's paths is 233's N1 test fix in `stack-upgrade.test.mjs`. Row 234
|
||||||
|
then landed as c771a36f4 on 57f59e0c3. Sage preferred that the gate run with it in the tree (sage-1773), so both
|
||||||
|
commits were picked onto c771a36f4 as `darkwing/row240-r3`. That was a clean pick: the 42 paths changed from
|
||||||
|
57f59e0c3 to c771a36f4 share none with this row's 9.
|
||||||
|
|
||||||
- `scripts/case1-pins.sh` (new, 0644): `PIN_PROFILES_VERSION`, `PIN_PROFILE_SHA256`, `PIN_BUBBLEWRAP_VERSION`,
|
- `scripts/case1-pins.sh` (new, 0644): `PIN_PROFILES_VERSION`, `PIN_PROFILE_SHA256`, `PIN_BUBBLEWRAP_VERSION`,
|
||||||
r6 section 0's values.
|
r6 section 0's values.
|
||||||
@@ -82,6 +85,13 @@ r6's case groups (:843-856) against the tests:
|
|||||||
The last test also checks that the repo script reads `scripts/case1-pins.sh` beside it, that bad usage exits
|
The last test also checks that the repo script reads `scripts/case1-pins.sh` beside it, that bad usage exits
|
||||||
2, and that a non-root run without `--root` refuses.
|
2, and that a non-root run without `--root` refuses.
|
||||||
|
|
||||||
|
Singles are the two files that run a changed script: `case1-hostcheck.test.mjs` and `stack-upgrade.test.mjs`.
|
||||||
|
Sage asked (sage-1759) whether `stack-release.test.mjs` or `stack-release-external.test.mjs`, which share
|
||||||
|
`stack-release-fixture.mjs`, run `stack-upgrade.sh` or `case1-pins.sh`. They don't. `grep -cF` for
|
||||||
|
`stack-upgrade`, `case1-pins`, `case1-hostcheck` and `hostcheck` gives 0 in all three files; the control
|
||||||
|
`stack-release.sh` gives 2 in the fixture and 8 in `stack-release.test.mjs`. `scripts/stack-release.sh` names
|
||||||
|
`stack-upgrade.sh` once, in a comment (:2061). The gate's cli suite runs both files anyway.
|
||||||
|
|
||||||
## Mutants
|
## Mutants
|
||||||
|
|
||||||
r6's seven (:858-860) and one for I3 N1, scripted in `~/darkwing-scratch/r240/mutants.sh` with r233's method: a checked backup,
|
r6's seven (:858-860) and one for I3 N1, scripted in `~/darkwing-scratch/r240/mutants.sh` with r233's method: a checked backup,
|
||||||
|
|||||||
Reference in new issue
Block a user