Skip to content

Analyzer constants refactoring#59523

Closed
kitaisreal wants to merge 11 commits intoClickHouse:masterfrom
kitaisreal:analyzer-constants-refactoring
Closed

Analyzer constants refactoring#59523
kitaisreal wants to merge 11 commits intoClickHouse:masterfrom
kitaisreal:analyzer-constants-refactoring

Conversation

@kitaisreal
Copy link
Copy Markdown
Contributor

@kitaisreal kitaisreal commented Feb 2, 2024

Changelog category (leave one):

  • Not for changelog (changelog entry is not required)

@robot-ch-test-poll robot-ch-test-poll added the pr-not-for-changelog This PR should not be mentioned in the changelog label Feb 2, 2024
@robot-ch-test-poll
Copy link
Copy Markdown
Contributor

robot-ch-test-poll commented Feb 2, 2024 •
edited by robot-clickhouse
Loading

This is an automated comment for commit e093560 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
A SyncThere's no description for the check yet, please add it to tests/ci/ci_config.py:CHECK_DESCRIPTIONS⏳ pending
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
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⏳ pending
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❌ failure
Mergeable CheckChecks if all other necessary checks are successful❌ failure
Successful checks
Check nameDescriptionStatus
Docs checkBuilds and tests the documentation✅ 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

@novikd novikd self-assigned this Feb 2, 2024
@novikd novikd added the analyzer Issues and pull-requests related to new analyzer label Feb 2, 2024
@novikd novikd mentioned this pull request Feb 26, 2024
Closed
@novikd novikd mentioned this pull request Apr 3, 2024
Closed
@clickhouse-gh
Copy link
Copy Markdown
Contributor

clickhouse-gh bot commented Jun 25, 2024

Dear @novikd, this PR hasn't been updated for a while. You will be unassigned. Will you continue working on it? If so, please feel free to reassign yourself.

@alexey-milovidov
Copy link
Copy Markdown
Member

alexey-milovidov commented Jul 14, 2024

@novikd, you can close this PR and open it from you as an author. Because there is only a single "Test" commit from @kitaisreal, and then there is nothing.

@alexey-milovidov alexey-milovidov added the close in a month if not active This will be closed in case of no information label Aug 4, 2024
@kitaisreal kitaisreal closed this Aug 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

analyzer Issues and pull-requests related to new analyzer close in a month if not active This will be closed in case of no information 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.

4 participants

@kitaisreal @robot-ch-test-poll @alexey-milovidov @novikd