Skip to content

Backport #57141 to 23.8: Follow up to #56541#65080

Merged
kssenii merged 2 commits into23.8from
backport/23.8/57141
Jun 24, 2024
Merged

Backport #57141 to 23.8: Follow up to #56541#65080
kssenii merged 2 commits into23.8from
backport/23.8/57141

Conversation

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

@robot-ch-test-poll2 robot-ch-test-poll2 commented Jun 11, 2024

Original pull-request #57141
Cherry-pick pull-request #65079

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-ch-test-poll2 robot-ch-test-poll2 added the pr-backport Changes, backported to release branch. Do not use manually - automated use only! label Jun 11, 2024
@robot-clickhouse-ci-1
Copy link
Copy Markdown
Contributor

robot-clickhouse-ci-1 commented Jun 11, 2024 •
edited by robot-clickhouse-ci-2
Loading

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

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

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 image for serversThe 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
Push to DockerhubThe check for building and pushing the CI related docker images to docker hub✅ success
Stateful testsRuns stateful 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
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
Integration testsThe integration tests report. In parenthesis the package type is given, and in square brackets are the optional part/total tests❌ failure
Stateless testsRuns stateless functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc❌ failure

@kssenii
Copy link
Copy Markdown
Member

kssenii commented Jun 24, 2024

Integration tests (release)

test_storage_kerberized_hdfs
test_system_merges
test_format_schema_on_server

-- not related to changes

@kssenii kssenii merged commit 185ae73 into 23.8 Jun 24, 2024
@kssenii kssenii deleted the backport/23.8/57141 branch June 24, 2024 17:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@Algunenano Algunenano

@kssenii kssenii

Labels

pr-backport Changes, backported to release branch. Do not use manually - automated use only!

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@robot-ch-test-poll2 @robot-clickhouse-ci-1 @kssenii @Algunenano @robot-clickhouse