Repository navigation
[2026.10.7] test: run_qam_extent_vrfy timeout for the ubuntu-26.04 runner - #248
Merged
Merged
Conversation
GitHub moved ubuntu-latest from 24.04 to 26.04 between e1fe5c2's runs. Master itself has gone red on "ubuntu-latest gcc/clang default", "mutex pthreads-library" and "linux --enable-dtrace (USDT)", and so has every open PR. Neither failure is an engine change; the same tree passed on 24.04 (339e95e). 1. run_qam_extent_vrfy timed out (exit 124). Building its 770-extent queue fdatasyncs every extent file, so the run time is the host's fsync latency times ~775: 162 s on 24.04, 181 s on 26.04, against a 180 s timeout. The default timeout for this runner is now 600 s. The syncs were not removed in the test: the attempts tried (a large cache, DB_NOSYNC closes, a private env with DB_NOFLUSH) each moved the syncs elsewhere, and one changed case 2's verdict from DB_VERIFY_BAD to EINVAL. 2. run_dtrace_probes: "bpftrace usdt:bdb:txn__commit fired 0 times". The runner gave bpftrace a fixed 3 s head start before running 100 commits. bpftrace 0.25 (26.04) compiles a BTF vmlinux.h first and attaches later than that, so every commit ran before the probe was live. It now waits for a BEGIN probe's "ATTACHED" line (up to 120 s) and checks the sudo'd bpftrace through /proc, since kill -0 cannot signal a root process. Debian 12, bpftrace 0.17, --enable-dtrace: fired 102 times (100 commits run), PASS. (cherry picked from commit 81e44c2)
Contributor
Coccinelle convention checksNo new violations. ✅ Resolved since baseline (3) -- update dist/cocci/baseline.txt to lock these in. |
Contributor
ABI diff vs
|
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
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.
Backport of the
run_qam_extent_vrfyhalf of #242 (81e44c28c, cherry-picked with-x).GitHub's
ubuntu-latestimage moved to 26.04, andrun_qam_extent_vrfynow takes about 181 s against its 180 s timeout. Its run time is the host's fsync latency times about 775, one fsync per extent file. That failed "ubuntu-latest gcc/clang default" and "mutex pthreads-library" on every LTS PR, #239 and #247 included. The default timeout for this runner is now 600 s.The other half of #242, the dtrace probe wait, does not apply:
run_dtrace_probes.shis not on the LTS line, because the DTrace refresh came after v2026.10.7. It was dropped during the cherry-pick.Test-only; no library change. LTS gates L1–L3 are not affected.