Files
flamenet-messenger-android/.e2e-ref
T
Paul HittandClaude Opus 5 e48907077c Take the e2e poll vectors and check them in CI
The other half of a change that was split so F6 could land alone.

`PollTallyVectorTest` was written, passed locally, and failed in CI with
three AssertionErrors at line 40, which is "vectors not found". The
fixture lives in flamenet-e2e, CI clones that repo at the commit
`.e2e-ref` pins, and the file only existed on an unmerged branch. It
passed on a developer machine because there is a sibling checkout there
and the runner has none, which is exactly the gap the pin-and-clone
exists to close. Not a defect in the test; this repo's cross-repo
process working.

So now, in one commit as `.e2e-ref.md` asks: the pin moves to e2e main,
FLAMENET_POLL_VECTORS joins the export list and the existence check that
runs before the suite, and the test comes back.

That existence check is the reason the loop above it exists. A path that
silently does not exist puts the tests straight back where they were and
the failure reads as a protocol bug rather than a missing file.

Verified both ways it can be reached: with FLAMENET_POLL_VECTORS set, as
CI sets it, and with it unset so the sibling-checkout fallback is what
answers.

client 480, engine 723, app 652, no failures. The vector suite itself:
3 tests, 0 skipped, 0 failures.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-24 14:09:07 -04:00

2 lines
41 B
Plaintext

be8093f7c76c42cac5b826f40db95db372bdd34b