Skip to content

Backport #66898 to 24.4: [CI Fest] Better processing of broken parts and their projections (fixes rare cases of lost forever)#67480

Merged
tavplubix merged 1 commit into24.4from
backport/24.4/66898
Sep 3, 2024
Merged

Backport #66898 to 24.4: [CI Fest] Better processing of broken parts and their projections (fixes rare cases of lost forever)#67480
tavplubix merged 1 commit into24.4from
backport/24.4/66898

Conversation

@robot-ch-test-poll1
Copy link
Copy Markdown
Contributor

@robot-ch-test-poll1 robot-ch-test-poll1 commented Jul 30, 2024

Original pull-request #66898
Cherry-pick pull-request #67022

This pull-request is a last step of an automated backporting.
Treat it as a standard pull-request: look at the checks and resolve conflicts.
Merge it only if you intend to backport changes to the target branch, otherwise just close it.

@robot-clickhouse
Backport #66898 to 24.4: [CI Fest] Better processing of broken parts …
f30c2a7 
…and their projections (fixes rare cases of lost forever)
@robot-ch-test-poll1 robot-ch-test-poll1 added pr-backport Changes, backported to release branch. Do not use manually - automated use only! pr-bugfix Pull request with bugfix, not backported by default labels Jul 30, 2024
@robot-clickhouse
Copy link
Copy Markdown
Member

robot-clickhouse commented Jul 30, 2024 •
edited by robot-clickhouse-ci-2
Loading

This is an automated comment for commit f30c2a7 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
CI runningA meta-check that indicates the running CI. Normally, it's in success or pending state. The failed status indicates some problems with the PR⏳ pending
Stateful testsRuns stateful functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc❌ failure
Successful checks
Check nameDescriptionStatus
ClickHouse build checkBuilds ClickHouse in various configurations for use in further steps. You have to fix the builds that fail. Build logs often has enough information to fix the error, but you might have to reproduce the failure locally. The cmake options can be found in the build log, grepping for cmake. Use these options and follow the general build process✅ 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
Install packagesChecks that the built packages are installable in a clear environment✅ success
Stateless testsRuns stateless functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc✅ success
Stress testRuns stateless functional tests concurrently from several clients to detect concurrency-related errors✅ success

@tavplubix tavplubix merged commit 24a4836 into 24.4 Sep 3, 2024
@tavplubix tavplubix deleted the backport/24.4/66898 branch September 3, 2024 13:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@alesapin alesapin

@tavplubix tavplubix

Labels

pr-backport Changes, backported to release branch. Do not use manually - automated use only! pr-bugfix Pull request with bugfix, not backported by default

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@robot-ch-test-poll1 @robot-clickhouse @alesapin @tavplubix