Skip to content

Commit ae140f6

Browse files
committed
docs(s003): PROOF.md names the closing commit's sha; NOTES.md the close's run and a flake for 021
The closing correction names 567507d. The minutes table gains run 35538464458 (fips 3m46s). Finding 11 records the default leg's one red on that run, session_flow_test.exs:108 after a Gate crash on a sandbox ownership error, passed on rerun; owned by slice 021, listed as a fix(s021) follow-up. Signed-off-by: Ayla Croft <aylacroft@proton.me>
1 parent 567507d commit ae140f6

2 files changed

Lines changed: 16 additions & 0 deletions

File tree

‎slices/003-fips-build-leg/NOTES.md‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -125,6 +125,7 @@ touches the leg, whichever is first.
125125
| 35537793241 | fips | success | 3m19s |
126126
| 35538008648 | fips | success | 1m28s |
127127
| 35538136447 | fips | success | 2m03s |
128+
| 35538464458 | fips | success (the closing commit, 567507d) | 3m46s |
128129

129130
The image build is under three minutes on the hosted runner (OTP from source with the unused applications left
130131
out), so the schedule-and-on-demand fallback SLICE.md names was not needed; the push to the registry under the
@@ -138,3 +139,13 @@ pull; a rerun of the failed job after `fips-image` finishes is the procedure, an
138139
from OTP are DER, 103 to 104 bytes, not the 96 the slice table names.
139140
- Upstream: Hex's TLS version list (finding 3); OTP's HelloRetryRequest handling (#8470, finding 4).
140141
- The ten-run minutes table (above).
142+
143+
11. **A flake on the default leg at the close, owned by slice 021.** Run 35538464458, job `gate`, seed 306150:
144+
`test/trinity/permissions/session_flow_test.exs:108` (AC5 deny) collected events up to `approval_wait` and
145+
never saw the session resume; the same log shows `Trinity.Permissions.Gate` terminating on
146+
`DBConnection.OwnershipError` ("cannot find ownership process"), which reads as an expiry timer from an
147+
earlier test's request firing after that test's sandbox owner had exited, so the Gate crashed, restarted, and
148+
the decision was lost. The `fips` and `postgres` jobs of the same run passed the test, and the rerun of the
149+
job passed (264/265, then 265/265). Not touched here: it is 021's test isolation, and this slice's closing
150+
commit changed records only. **Follow-up, `fix(s021)`**: the Gate's expiry timers, or the test's sandbox
151+
allowance, need to outlive the test that armed them, or be cancelled on the owner's exit.

‎slices/003-fips-build-leg/PROOF.md‎

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -132,3 +132,8 @@ b74da2f fix(s003): the image's self-check matches enable_fips_mode/1's true
132132
ad8bc17 feat(s003): the FIPS image, the leg in the gate, the mode tests and the supports record
133133
7179cac docs(s003): G1 plan with the FIPS mechanism measured, and the slice opens
134134
```
135+
136+
## Closing correction, 2026-09-20
137+
Supersedes the header's "Final commit" placeholder: the closing commit is `567507d` (`feat(s003): complete slice
138+
003 (FIPS build leg)`), and this correction rides on the commit after it, which also names the CI run of the
139+
close in NOTES.md's minutes table.

0 commit comments

Comments
 (0)