Skip to content

[2026.10.7] test: run_qam_extent_vrfy timeout for the ubuntu-26.04 runner #248

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
gburd merged 1 commit into from
Nov 3, 2026
Merged

[2026.10.7] test: run_qam_extent_vrfy timeout for the ubuntu-26.04 runner #248

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
9 changes: 8 additions & 1 deletion test/db/run_qam_extent_vrfy.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,14 @@ BUILD=${BUILD:-.}
_HERE=$(cd "$(dirname "$0")" && pwd)
SRC=${SRC:-$_HERE/qam_extent_vrfy.c}
HOME_DIR=${HOME_DIR:-QAM_EXTENT_VRFY_TESTDIR}
TIMEOUT=${TIMEOUT:-180}
# 600 s, not the usual 180 s: building the many-extent queue fdatasyncs each of
# its ~775 extent files (eviction-discard during the fill and the per-file sync at
# close), so the run time is the host's fsync latency times 775. That was
# 162 s on GitHub's ubuntu-24.04 runners and 181 s on ubuntu-26.04, which timed
# out at 180 s. The I/O pattern is what the test exercises; do not shorten it by
# skipping syncs (DB_NOSYNC + DB_NOFLUSH changed case 2's verdict from
# DB_VERIFY_BAD to EINVAL).
TIMEOUT=${TIMEOUT:-600}

# Prefer the STATIC library: on macOS the .dylib carries a baked-in install name
# (/usr/local/BerkeleyDB.5.3/lib/...) which takes precedence over -rpath, so a
Expand Down
Loading