ci(load-test): exclude live DuckDB from artifact upload (fix flaky ENOENT)#212
Merged
Merged
Conversation
…ENOENT) The load-test job intermittently failed at "Upload load-test artifacts" with `ENOENT: ... agentflow-load.duckdb.wal`: DuckDB checkpoints and removes the .wal sidecar asynchronously, so it can vanish between upload-artifact's file scan and the zip step. Hit twice this session (PRs #208, #211), each cleared only by a rerun — a recurring false red on every PR and main push. Exclude the live DuckDB files (`*.duckdb`, `*.duckdb.*`) from the uploaded artifact. They are runtime state, not debug output (results.json, stats and api.log are kept), so the step is now deterministic instead of racing the checkpoint. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
DORA Metrics
|
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
2 participants
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.
Problem
The
load-testjob intermittently fails at Upload load-test artifacts with:DuckDB checkpoints and removes the
.walsidecar asynchronously, so it can vanish betweenupload-artifact's file enumeration and the zip step. Seen twice this session (PRs #208 and #211); each was a false red cleared only by a rerun, on both PR and main-push runs.Fix
Exclude the live DuckDB files (
*.duckdb,*.duckdb.*) from the uploaded artifact. They are runtime state, not debug output —results.json, the stats files andapi.logare still uploaded — so the step becomes deterministic instead of racing the checkpoint.No change to what the load gate measures.
🤖 Generated with Claude Code