Skip to content

Do not fail targeted integration checks on session timeout#96761

Merged
alexey-milovidov merged 1 commit intomasterfrom
fix-targeted-integration-timeout
Feb 12, 2026
Merged

Do not fail targeted integration checks on session timeout#96761
alexey-milovidov merged 1 commit intomasterfrom
fix-targeted-integration-timeout

Conversation

@alexey-milovidov
Copy link
Copy Markdown
Member

@alexey-milovidov alexey-milovidov commented Feb 12, 2026

Summary

  • Targeted integration checks run previously-failed tests with --count 10 to detect flakiness
  • For slow test suites like test_database_delta (Spark/Unity Catalog, ~30-60s per test), the 1200s session timeout is easily exceeded even when all completed tests pass
  • The code already avoids setting the has_error flag for targeted checks (recognizing session-timeout as an expected risk), but the synthetic Timeout FAIL result was still propagated into the final results, causing the job to be reported as failed
  • Filter out the Timeout pseudo-result for targeted checks so the job status reflects only actual test outcomes

CI report: https://s3.amazonaws.com/clickhouse-test-reports/json.html?PR=96506&sha=ea37810a1e3427e90315554d5cab63fc080a50a3&name_0=PR&name_1=Integration%20tests%20%28amd_asan%2C%20targeted%29
#96506

Changelog category (leave one):

  • CI Fix or improvement

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):

  • Do not fail targeted integration checks on session timeout when all completed tests have passed.

🤖 Generated with Claude Code

The targeted integration check runs previously-failed tests with
`--count 10` to detect flakiness. For slow test suites like
`test_database_delta` (which uses Spark/Unity Catalog containers,
~30-60s per test), the 1200s session timeout is easily exceeded
even when all completed tests pass.

The code already avoids setting the `has_error` flag for targeted
checks (lines 571-576), recognizing that session-timeout is an
expected risk. However, the synthetic `Timeout` FAIL result added
by `run_pytest_and_collect_results` was still propagated into the
final results, causing the job to be reported as failed.

Filter out the `Timeout` pseudo-result for targeted checks so that
the job status reflects only actual test outcomes.

https://s3.amazonaws.com/clickhouse-test-reports/json.html?PR=96506&sha=ea37810a1e3427e90315554d5cab63fc080a50a3&name_0=PR&name_1=Integration%20tests%20%28amd_asan%2C%20targeted%29

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@clickhouse-gh
Copy link
Copy Markdown
Contributor

clickhouse-gh Bot commented Feb 12, 2026

Workflow [PR], commit [431dae6]

Summary:

@alexey-milovidov alexey-milovidov self-assigned this Feb 12, 2026
@alexey-milovidov alexey-milovidov added this pull request to the merge queue Feb 12, 2026
Merged via the queue into master with commit b671709 Feb 12, 2026
134 checks passed
@alexey-milovidov alexey-milovidov deleted the fix-targeted-integration-timeout branch February 12, 2026 19:29
@robot-ch-test-poll robot-ch-test-poll added the pr-synced-to-cloud The PR is synced to the cloud repo label Feb 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr-synced-to-cloud The PR is synced to the cloud repo

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants