Skip to content

ci(load-test): exclude live DuckDB from artifact upload (fix flaky ENOENT) #212

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
brownjuly2003-code merged 1 commit into from
Jul 19, 2026
Merged

ci(load-test): exclude live DuckDB from artifact upload (fix flaky ENOENT) #212

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion .github/workflows/load-test.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,4 +69,12 @@ jobs:
uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
with:
name: load-test-results
path: .artifacts/load/
# Exclude the live DuckDB files: their .wal sidecar is checkpointed away
# asynchronously, so it can vanish between upload-artifact's file scan and
# the zip step, failing the job with ENOENT on `*.duckdb.wal`. The DBs are
# runtime state, not useful debug output (results.json / stats / api.log
# are). This makes the step deterministic instead of racing the checkpoint.
path: |
.artifacts/load/
!.artifacts/load/*.duckdb
!.artifacts/load/*.duckdb.*