Repository navigation
test(e2e): rewrite audit journal tests against the real format and gate them in CI - #624
Merged
Merged
Conversation
…te them in CI make test-audit hung for over 40 minutes and had never passed: A1-A11 expected one age-encrypted file per entry decryptable by RSSI/DPO personas from crypto/rssi.key, a design that was never built (the keys did not even exist), and A12/A13 re-read the whole 300 MB journal spawning python per line. The audit journal is a signed, hash-chained plaintext JSONL file. The new suite checks that contract: files and key permissions, ECDSA P-256 signature of each entry over the hash the next entry chains to (window of 200), tamper rejection, EU AI Act fields on RESPONSE entries and the NC/C1/C2 classification levels. It runs in seconds and is added to the CI E2E job after the hurl suites. advanced/S4 read the last journal line, which can be a reload entry; it now checks the latest RESPONSE entry. The age tooling, crypto/ generator and RTM rows for the unbuilt design are removed.
Destynova2
enabled auto-merge (squash)
September 27, 2026 17:51
Destynova2
added a commit
that referenced
this pull request
Sep 27, 2026
## 🤖 New release * `grob`: 0.36.119 -> 0.36.120 <details><summary><i><b>Changelog</b></i></summary><p> <blockquote> ## [0.36.120](v0.36.119...v0.36.120) - 2026-09-27 ### Other - compose GeminiProvider from ProviderBase and split the two oversized modules ([#625](#625)) - *(e2e)* rewrite audit journal tests against the real format and gate them in CI ([#624](#624)) </blockquote> </p></details> --- This PR was generated with [release-plz](https://github.com/release-plz/release-plz/).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
make test-audit hung for over 40 minutes and had never passed: A1-A11
expected one age-encrypted file per entry decryptable by RSSI/DPO
personas from crypto/rssi.key, a design that was never built (the keys
did not even exist), and A12/A13 re-read the whole 300 MB journal
spawning python per line.
The audit journal is a signed, hash-chained plaintext JSONL file. The new
suite checks that contract: files and key permissions, ECDSA P-256
signature of each entry over the hash the next entry chains to (window
of 200), tamper rejection, EU AI Act fields on RESPONSE entries and the
NC/C1/C2 classification levels. It runs in seconds and is added to the
CI E2E job after the hurl suites.
advanced/S4 read the last journal line, which can be a reload entry; it
now checks the latest RESPONSE entry. The age tooling, crypto/ generator
and RTM rows for the unbuilt design are removed.
Validation (local podman pod, fresh audit dir)
make test-hurl9/9 →make test-audit6/6 in ~5 s (previously hung >40 min, never passed)make test-advanced3 runs: 10/10, 9/10+1 skip (S5 HIT flow, pre-existing skip), no S4 failure