Export the poll vectors in vectors-head too
The pinned job got FLAMENET_POLL_VECTORS and this one did not, so PollTallyVectorTest ran here with no vectors to read and failed three times, including its own control. It only reached the board as a green pipeline because the job carries allow_failure, and a check that always fails is noise. The sibling-checkout fallback covers a developer machine and nothing on the runner, which clones e2e into .ci-vectors-head instead. Reproduced the job locally against e2e at HEAD, which is the same commit as the pin: 723 engine tests, no failures, the vector suite itself 3 of 3 with none skipped. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5
parent
e48907077c
commit
f1cd145c5c
@@ -205,6 +205,7 @@ vectors-head:
|
|||||||
- export FLAMENET_BACKUP_VECTORS="$CI_PROJECT_DIR/.ci-vectors-head/test/vectors/backup-v1.json"
|
- export FLAMENET_BACKUP_VECTORS="$CI_PROJECT_DIR/.ci-vectors-head/test/vectors/backup-v1.json"
|
||||||
- export FLAMENET_BACKUP_PAYLOAD_VECTORS="$CI_PROJECT_DIR/.ci-vectors-head/test/vectors/backup-payload-v1.json"
|
- export FLAMENET_BACKUP_PAYLOAD_VECTORS="$CI_PROJECT_DIR/.ci-vectors-head/test/vectors/backup-payload-v1.json"
|
||||||
- export FLAMENET_CONTENT_VECTORS="$CI_PROJECT_DIR/.ci-vectors-head/test/vectors/content-v1.json"
|
- export FLAMENET_CONTENT_VECTORS="$CI_PROJECT_DIR/.ci-vectors-head/test/vectors/content-v1.json"
|
||||||
|
- export FLAMENET_POLL_VECTORS="$CI_PROJECT_DIR/.ci-vectors-head/test/vectors/poll-tally-v1.json"
|
||||||
# Only the module that reads vectors. The rest of the suite has nothing
|
# Only the module that reads vectors. The rest of the suite has nothing
|
||||||
# to say about whether flamenet-e2e moved, and running it here would double
|
# to say about whether flamenet-e2e moved, and running it here would double
|
||||||
# the board's cost to answer a question it cannot answer.
|
# the board's cost to answer a question it cannot answer.
|
||||||
|
|||||||
Reference in New Issue
Block a user