Skip to content

tests: use compact output for skip reason in clickhouse-test launcher#75530

Closed
azat wants to merge 1 commit intoClickHouse:masterfrom
azat:tests/compact-launcher
Closed

tests: use compact output for skip reason in clickhouse-test launcher#75530
azat wants to merge 1 commit intoClickHouse:masterfrom
azat:tests/compact-launcher

Conversation

@azat
Copy link
Copy Markdown
Member

@azat azat commented Feb 4, 2025

Changelog category (leave one):

  • Not for changelog (changelog entry is not required)

@azat azat requested a review from fm4v February 4, 2025 16:49
@azat azat mentioned this pull request Feb 4, 2025
Merged
21 tasks
@robot-ch-test-poll3 robot-ch-test-poll3 added the pr-not-for-changelog This PR should not be mentioned in the changelog label Feb 4, 2025
@robot-ch-test-poll3
Copy link
Copy Markdown
Contributor

robot-ch-test-poll3 commented Feb 4, 2025 •
edited by robot-ch-test-poll1
Loading

This is an automated comment for commit 236a97f 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
ClickBenchRuns ClickBench with instant-attach table✅ success
Compatibility checkChecks that clickhouse binary runs on distributions with old libc versions. If it fails, ask a maintainer for help✅ success
Docker keeper imageThe check to build and optionally push the mentioned image to docker hub✅ success
Docker server imageThe check to build and optionally push the mentioned image to docker hub✅ 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
Install packagesChecks that the built packages are installable in a clear environment✅ success
Integration testsThe integration tests report. In parenthesis the package type is given, and in square brackets are the optional part/total tests✅ success
Performance ComparisonMeasure changes in query performance. The performance test report is described in detail here. In square brackets are the optional part/total tests✅ success
Stress testRuns stateless functional tests concurrently from several clients to detect concurrency-related errors✅ 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
Upgrade checkRuns stress tests on server version from last release and then tries to upgrade it to the version from the PR. It checks if the new server can successfully startup without any errors, crashes or sanitizer asserts✅ success

@fm4v
Copy link
Copy Markdown
Member

fm4v commented Feb 4, 2025

The idea is to display the test failure reason in the HTML report and this PR will hide it.

Screenshot From 2025-02-04 17-55-33

@azat
Copy link
Copy Markdown
Member Author

azat commented Feb 4, 2025

The idea is to display the test failure reason in the HTML report and this PR will hide it.

I see, I was talking about skips

@azat azat marked this pull request as draft February 4, 2025 17:04
@azat azat closed this Feb 11, 2025
@azat azat deleted the tests/compact-launcher branch February 11, 2025 11:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@fm4v fm4v Awaiting requested review from fm4v

Assignees

No one assigned

Labels

pr-not-for-changelog This PR should not be mentioned in the changelog

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@azat @robot-ch-test-poll3 @fm4v