Skip to content

release-26.1: server: deflake TestStatusAPIContentionEvents contention event check#170000

Merged
trunk-io[bot] merged 1 commit into
cockroachdb:release-26.1from
dhartunian:backport26.1-169156
May 9, 2026
Merged

release-26.1: server: deflake TestStatusAPIContentionEvents contention event check#170000
trunk-io[bot] merged 1 commit into
cockroachdb:release-26.1from
dhartunian:backport26.1-169156

Conversation

@dhartunian
Copy link
Copy Markdown
Collaborator

Backport 1/1 commits from #169156.

/cc @cockroachdb/release


The test queried the contention events HTTP endpoint once and
immediately asserted the test table's event was present. But
contention events are collected asynchronously — the existing
WaitForTransactionEntriesAtLeast call only waits for transaction
stats (a different subsystem), so the contention event may not
have been ingested yet. Under race builds or slow CI, this
manifests as finding system table contention but not the test
table's contention.

Wrap the contention event HTTP query and table-ID check in
testutils.SucceedsSoon, matching the retry pattern already used
for statement and transaction stats later in the same test.

Fixes: #169050
Epic: none

Release note: None


Release justification: test-only deflake

The test queried the contention events HTTP endpoint once and
immediately asserted the test table's event was present. But
contention events are collected asynchronously — the existing
WaitForTransactionEntriesAtLeast call only waits for transaction
stats (a different subsystem), so the contention event may not
have been ingested yet. Under race builds or slow CI, this
manifests as finding system table contention but not the test
table's contention.

Wrap the contention event HTTP query and table-ID check in
testutils.SucceedsSoon, matching the retry pattern already used
for statement and transaction stats later in the same test.

Fixes: cockroachdb#169050
Epic: none

Release note: None

Co-Authored-By: roachdev-claude <roachdev-claude-bot@cockroachlabs.com>
@dhartunian dhartunian requested a review from a team as a code owner May 8, 2026 20:04
@dhartunian dhartunian requested review from alyshanjahani-crl and removed request for a team May 8, 2026 20:04
@blathers-crl
Copy link
Copy Markdown

blathers-crl Bot commented May 8, 2026

Thanks for opening a backport.

Before merging, please confirm that the change does not break backwards compatibility and otherwise complies with the backport policy. Include a brief release justification in the PR description explaining why the backport is appropriate. All backports must be reviewed by the TL for the owning area. While the stricter LTS policy does not yet apply, please exercise judgment and consider gating non-critical changes behind a disabled-by-default feature flag when appropriate.

@trunk-io
Copy link
Copy Markdown
Contributor

trunk-io Bot commented May 8, 2026

😎 Merged successfully - details.

@blathers-crl blathers-crl Bot added backport Label PR's that are backports to older release branches T-observability labels May 8, 2026
@cockroach-teamcity
Copy link
Copy Markdown
Member

This change is Reviewable

@blathers-crl
Copy link
Copy Markdown

blathers-crl Bot commented May 8, 2026

Detected infrastructure failure (matched: self-hosted runner lost communication with the server). Automatically rerunning failed jobs. (run link)

@blathers-crl blathers-crl Bot added backport-failed backport-test-only Used to denote the backport has only non-production changes and removed backport-failed labels May 8, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 9, 2026

/trunk merge

@trunk-io trunk-io Bot merged commit c704ba1 into cockroachdb:release-26.1 May 9, 2026
31 of 32 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport Label PR's that are backports to older release branches backport-test-only Used to denote the backport has only non-production changes T-observability target-release-26.1.5

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants