Skip to content

Follow-up to #59767#64398

Merged
kssenii merged 1 commit intomasterfrom
follow-up-to-59767
May 26, 2024
Merged

Follow-up to #59767#64398
kssenii merged 1 commit intomasterfrom
follow-up-to-59767

Conversation

@kssenii
Copy link
Copy Markdown
Member

@kssenii kssenii commented May 25, 2024

Changelog category (leave one):

  • Not for changelog (changelog entry is not required)

Follow up to #59767

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

...

Documentation entry for user-facing changes

  • Documentation is written (mandatory for new features)

Information about CI checks: https://clickhouse.com/docs/en/development/continuous-integration/

CI Settings

NOTE: If your merge the PR with modified CI you MUST KNOW what you are doing
NOTE: Checked options will be applied if set before CI RunConfig/PrepareRunConfig step

  • Allow: Integration Tests
  • Allow: Stateless tests
  • Allow: Stateful tests
  • Allow: Upgrade tests
  • Allow: Stress tests
  • Allow: Unit tests
  • Allow: Performance tests
  • Allow: All with aarch64
  • Allow: All with ASAN
  • Allow: All with TSAN
  • Allow: All with Analyzer
  • Allow: All with Azure
  • Allow: Add your option here

  • Exclude: Fast test
  • Exclude: Integration Tests
  • Exclude: Stateless tests
  • Exclude: Stateful tests
  • Exclude: Performance tests
  • Exclude: All with ASAN
  • Exclude: All with TSAN
  • Exclude: All with MSAN
  • Exclude: All with UBSAN
  • Exclude: All with Coverage
  • Exclude: All with Aarch64

  • do not test (only style check)
  • disable merge-commit (no merge from master before tests)
  • disable CI cache (job reuse)
  • allow: batch 1 for multi-batch jobs
  • allow: batch 2
  • allow: batch 3
  • allow: batch 4, 5 and 6

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

robot-ch-test-poll4 commented May 25, 2024

This is an automated comment for commit 031591f 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
Stress testRuns stateless functional tests concurrently from several clients to detect concurrency-related errors❌ failure
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❌ failure
Successful checks
Check nameDescriptionStatus
A SyncThere's no description for the check yet, please add it to tests/ci/ci_config.py:CHECK_DESCRIPTIONS✅ success
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✅ success
Docs checkBuilds and tests the documentation✅ success
Mergeable CheckChecks if all other necessary checks are successful✅ success
PR CheckThere's no description for the check yet, please add it to tests/ci/ci_config.py:CHECK_DESCRIPTIONS✅ 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

@kssenii
Copy link
Copy Markdown
Member Author

kssenii commented May 26, 2024

Stress test

Something strange (OOM), but should not be related to changes

Upgrade check (debug)

Ok, no longer settings from #59767

@kssenii kssenii self-assigned this May 26, 2024
@kssenii kssenii added this pull request to the merge queue May 26, 2024
Merged via the queue into master with commit 2c3c0d0 May 26, 2024
@kssenii kssenii deleted the follow-up-to-59767 branch May 26, 2024 09:15
@robot-ch-test-poll4 robot-ch-test-poll4 added the pr-synced-to-cloud The PR is synced to the cloud repo label May 26, 2024
@tavplubix
Copy link
Copy Markdown
Member

Stress test

Something strange (OOM), but should not be related to changes

@kssenii there was a very interesting failure:

Stress test (azure, msan) — Possible deadlock on shutdown (see gdb.log) Details

[ 18201 ] {50b8cddb-04c4-4bd2-becb-120d54e77798} <Fatal> : Logical error: \'outcome_future.valid()\'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr-not-for-changelog This PR should not be mentioned in the changelog 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.

3 participants