Skip to content

[CI Party] Fix flaky window view tests#67097

Closed
rschu1ze wants to merge 1 commit intoClickHouse:masterfrom
rschu1ze:unflake-win-view-tests
Closed

[CI Party] Fix flaky window view tests#67097
rschu1ze wants to merge 1 commit intoClickHouse:masterfrom
rschu1ze:unflake-win-view-tests

Conversation

@rschu1ze
Copy link
Copy Markdown
Member

Fixes #65583

The issue ^^ is technically only about 01075_window_view_proc_tumble_to_now_populate but almost all window view tests are affected, so this PR fixes them all.

Changelog category (leave one):

  • Not for changelog (changelog entry is not required)

@robot-ch-test-poll2 robot-ch-test-poll2 added the pr-not-for-changelog This PR should not be mentioned in the changelog label Jul 25, 2024
@rschu1ze rschu1ze force-pushed the unflake-win-view-tests branch from 41fe980 to 0358755 Compare July 25, 2024 08:38
@rschu1ze rschu1ze added the 🍃 green ci 🌿 Fixing flaky tests in CI label Jul 25, 2024
"--allow_experimental_analyzer=0"
)

db="$(random_str 10)"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

you can use CLICKHOUSE_TEST_UNIQUE_NAME

DROP TABLE IF EXISTS mt;
DROP TABLE IF EXISTS dst;
DROP TABLE IF EXISTS wv;
DROP DATABASE IF EXISTS ${db};
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This should be automatic. Each test runs under $CLICKHOUSE_DATABASE. If we need to manually create it it's either because we are doing extremely special (which we aren't in this case), a bad test or a bug.

@kssenii kssenii self-assigned this Jul 25, 2024
@robot-ch-test-poll1
Copy link
Copy Markdown
Contributor

robot-ch-test-poll1 commented Jul 25, 2024

This is an automated comment for commit 0358755 with description of existing statuses. It's updated for the latest CI running

❌ Click here to open a full report in a separate page

Check nameDescriptionStatus
Stateless testsRuns stateless functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc❌ failure
Successful checks
Check nameDescriptionStatus
BuildsThere's no description for the check yet, please add it to tests/ci/ci_config.py:CHECK_DESCRIPTIONS✅ success
Docs checkBuilds and tests the documentation✅ success
Fast testNormally this is the first check that is ran for a PR. It builds ClickHouse and runs most of stateless functional tests, omitting some. If it fails, further checks are not started until it is fixed. Look at the report to see which tests fail, then reproduce the failure locally as described here✅ success
Flaky testsChecks if new added or modified tests are flaky by running them repeatedly, in parallel, with more randomization. Functional tests are run 100 times with address sanitizer, and additional randomization of thread scheduling. Integration tests are run up to 10 times. If at least once a new test has failed, or was too long, this check will be red. We don't allow flaky tests, read the doc✅ success
Style checkRuns a set of checks to keep the code style clean. If some of tests failed, see the related log from the report✅ success
Unit testsRuns the unit tests for different release types✅ success

@rschu1ze
Copy link
Copy Markdown
Member Author

Closed in favor of #67130

Also see #65583 (comment)

@rschu1ze rschu1ze closed this Jul 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🍃 green ci 🌿 Fixing flaky tests in CI pr-not-for-changelog This PR should not be mentioned in the changelog

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Stateless 01075_window_view_proc_tumble_to_now_populate is flaky

6 participants