Skip to content

release-26.2: sql/importer: fix TestUniqueUUID timeout#166347

Open
blathers-crl[bot] wants to merge 1 commit intorelease-26.2from
blathers/backport-release-26.2-166309
Open

release-26.2: sql/importer: fix TestUniqueUUID timeout#166347
blathers-crl[bot] wants to merge 1 commit intorelease-26.2from
blathers/backport-release-26.2-166309

Conversation

@blathers-crl
Copy link

@blathers-crl blathers-crl bot commented Mar 21, 2026

Backport 1/1 commits from #166309 on behalf of @mw5h.


Summary

Disable elastic CPU control in TestUniqueUUID to prevent the test from
exceeding the 15m timeout. The test imports 50,000 rows across three
tables with UUID/random primary key defaults.

When the metamorphic constant import-row-count-validation selects
sync mode, each import synchronously waits for an INSPECT validation
job that scans the imported data. Combined with elastic CPU throttling
(which was recently enabled for import jobs), the cumulative scan time
across the three imports can exceed the test timeout.

This mirrors the fix applied to other import tests in bda9189.

Resolves: #166130
Epic: None

🤖 Generated with Claude Code


Release justification:

Disable elastic CPU control in TestUniqueUUID to prevent the test from
exceeding the 15m timeout. The test imports 50,000 rows across three
tables with UUID/random primary key defaults.

When the metamorphic constant `import-row-count-validation` selects
`sync` mode, each import synchronously waits for an INSPECT validation
job that scans the imported data. Combined with elastic CPU throttling
(which was recently enabled for import jobs), the cumulative scan time
across the three imports can exceed the test timeout.

This mirrors the fix applied to other import tests in bda9189.

Resolves: #166130
Epic: None
Release note: None

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@blathers-crl blathers-crl bot requested a review from a team as a code owner March 21, 2026 00:27
@blathers-crl blathers-crl bot force-pushed the blathers/backport-release-26.2-166309 branch from 5f1518b to 673fe25 Compare March 21, 2026 00:27
@blathers-crl blathers-crl bot requested review from ZhouXing19 and removed request for a team March 21, 2026 00:27
@blathers-crl blathers-crl bot added blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. labels Mar 21, 2026
@blathers-crl
Copy link
Author

blathers-crl bot commented Mar 21, 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.

@blathers-crl blathers-crl bot added backport Label PR's that are backports to older release branches T-sql-queries SQL Queries Team labels Mar 21, 2026
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@blathers-crl blathers-crl bot added the backport-test-only Used to denote the backport has only non-production changes label Mar 21, 2026
Copy link
Member

@yuzefovich yuzefovich left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yuzefovich reviewed 1 file and all commit messages.
Reviewable status: :shipit: complete! 0 of 0 LGTMs obtained (waiting on DrewKimball and ZhouXing19).

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 blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. T-sql-queries SQL Queries Team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants