Dashboard for pull requests of https://github.com/clickhouse/clickhouse

Data was updated

If you're not running this app locally, consider updating the page with F5 -- database is updated once in ~10 minutes, while the API rate is limited

Still want to refresh Reload the page






Author Title Tests Details Labels Changes Reviewed Last event Assignees Requested reviewers

alexey-milovidov
MEMBER
[15263] Add more hardware results

Created

Changelog category (leave one): - Documentation (changelog entry is not required) Continuation of https://github.com/ClickHouse/ClickHouse/pull/15115


Marker check
Fast test


pr-documentation
5 commits created
lines: + 227, - 7
227 lines added
7 lines deleted

alexey-milovidov
MEMBER
[15260] Avoid deadlocks in Log/TinyLog (part 2)

Created

Merging #14962 Category: - Not for changelog.



Description check

pr-not-for-changelog
1 commits created
lines: + 307, - 79
307 lines added
79 lines deleted

added a label

alexey-milovidov
MEMBER
[15258] Fix MSan report in QueryLog

Created

Changelog category (leave one): - Bug Fix Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md): Fix MSan report in QueryLog. Uninitialized memory can be used for the field `memory_usage`. Details: https://clickhouse-test-reports.s3.yandex.net/15240/dce6a436f37713224c242092446e1a9fcf8b4a4a/stress_test_(memory)/stderr.log Remaining questions: - why a query may not heave a thread group at this moment? - why did not reproduce earlier?




bugfest
pr-bugfix
1 commits created
lines: + 1, - 1
1 lines added
1 lines deleted

added a label

robot-clickhouse
MEMBER
[14968] Backport #14937 to 20.6: Fix enable_optimize_predicate_expression for finalizeAggregation

Created

Original pull-request #14937 Cherry-pick pull-request #14966 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.




pr-backport
2 commits created
lines: + 53, - 5
53 lines added
5 lines deleted

robot-clickhouse
MEMBER
[14971] Backport #14937 to 20.9: Fix enable_optimize_predicate_expression for finalizeAggregation

Created

Original pull-request #14937 Cherry-pick pull-request #14964 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.


Marker check
ClickHouse build check


pr-backport
2 commits created
lines: + 53, - 5
53 lines added
5 lines deleted

robot-clickhouse
MEMBER
[14970] Backport #14937 to 20.7: Fix enable_optimize_predicate_expression for finalizeAggregation

Created

Original pull-request #14937 Cherry-pick pull-request #14965 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.




pr-backport
2 commits created
lines: + 53, - 5
53 lines added
5 lines deleted

robot-clickhouse
MEMBER
[14969] Backport #14937 to 20.8: Fix enable_optimize_predicate_expression for finalizeAggregation

Created

Original pull-request #14937 Cherry-pick pull-request #14967 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.


Marker check
ClickHouse build check


pr-backport
2 commits created
lines: + 53, - 5
53 lines added
5 lines deleted

crakjie
[15231] Back port #14937 "Fix enable_optimize_predicate_expression for finalizeAggregation" to 20.3 LTS

Created

Back port #14937 to 20.3 LTS finalizeAggregation was wrongly marked as stateful, preventing pushing the conditions down. I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en Changelog category (leave one): - Not for changelog (changelog entry is not required)



Split build smoke test
ClickHouse build check

can be tested
pr-backport
pr-not-for-changelog
2 commits created
lines: + 53, - 5
53 lines added
5 lines deleted

alesapin
MEMBER
[15239] 100% lld-11 for clang-11 builds

Created

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en Changelog category (leave one): - Not for changelog (changelog entry is not required) Do not merge.

Description check
Style check
Docs check
Push to dockerhub
Yandex third-party checks (only for Yandex employees)
Fast test
PVS check
Split build smoke test
Functional stateful tests (debug)
Functional stateful tests (release)
Compatibility check
Functional stateful tests (ubsan)
Functional stateful tests (release, DatabaseAtomic)
Functional stateful tests (thread)
Functional stateful tests (address)
Unit tests TSAN
Unit tests release gcc
Unit tests MSAN
Unit tests release clang
Unit tests UBSAN
Marker check
Unit tests ASAN
Functional stateful tests (memory)
Testflows check
Functional stateless tests (release, polymorphic parts enabled)
Functional stateless tests (ubsan)
Stress test (undefined)
Functional stateless tests (address)
Stress test (address)
Functional stateless tests (memory)
Functional stateless tests (debug)
Integration tests (release)
Functional stateless tests (thread)


1
pr-not-for-changelog
1 commits created
lines: + 6, - 19
6 lines added
19 lines deleted

tavplubix
MEMBER
[15003] Enable Atomic database engine by default

Created

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en Changelog category (leave one): - Improvement Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md): Enable `Atomic` database engine by default




2
force tests
pr-improvement
11 commits created
lines: + 591, - 392
591 lines added
392 lines deleted

azat
COLLABORATOR
[15007] Convert to python3

Created

Changelog category (leave one): - Build/Testing/Packaging Improvement Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md): Convert to python3. This closes #14886 Detailed description / Documentation draft: python2 is already EOL, [since January 1, 2020](https://www.python.org/doc/sunset-python-2/) Tech checklist: <details> - [x] tests (via `2to3`) - [x] scripts (via `2to3`) - [x] scripts (via `sed, package list) - [x] some documentation - [x] Dockerfile (via `sed`, package list) - [x] pip (via `s/pip/python3 -m pip/`) - [x] shebang's (via `sed`) </details> Checklist: - [x] scripts - [x] stateless tests - [x] stateful tests - [ ] integration tests - [ ] `tests/external_models/catboost/data/build_catboost.sh` left as-is, since it uses some `ya` command (cc @KochetovNicolai) P.S I used `2to3` and it was OK, I guess for massive converting it is to use it. P.P.S. some commits have commands, that has been executed to update files Cc: @alexey-milovidov Cc: @alesapin Refs: #15006 Refs: https://github.com/ClickHouse/ClickHouse/pull/10562#issuecomment-620823559



Integration tests (asan)
Integration tests (release)
Functional stateless tests (release)
Marker check

10
pr-build
68 commits created
lines: + 1505, - 1328
1505 lines added
1328 lines deleted


robot-clickhouse
MEMBER
[15256] Backport #14879 to 20.3: Segfault in CacheDictionary

Created

Original pull-request #14879 Cherry-pick pull-request #15254 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.



Split build smoke test
ClickHouse build check
Stress test (undefined)
Marker check

pr-backport
1 commits created
lines: + 13, - 9
13 lines added
9 lines deleted

added a label

ianton-ru
[15238] Use S3 multi object delete

Created

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en Changelog category (leave one): - Performance Improvement Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md): Use one S3 DeleteObjects request instead of multiple DeleteObject in cycle. No any functionality changes, so covered by existing tests like integration/test_log_family_s3.

Description check
Docs check
Style check
Push to dockerhub
Fast test
PVS check
Split build smoke test
Yandex third-party checks (only for Yandex employees)
Functional stateful tests (debug)
Compatibility check
Unit tests TSAN
Functional stateful tests (ubsan)
Unit tests UBSAN
Unit tests release gcc
Functional stateful tests (release)
Functional stateful tests (release, DatabaseAtomic)
Unit tests ASAN
Functional stateful tests (thread)
Functional stateful tests (address)
Testflows check
Unit tests MSAN
ClickHouse build check
Functional stateful tests (memory)
Marker check
Functional stateless tests (release)
ClickHouse special build check
Functional stateless tests (ubsan)
Stress test (thread)
Stress test (undefined)
Stress test (address)
Functional stateless tests (address)
Functional stateless tests (memory)
Functional stateless tests (debug)
Functional stateless tests (thread)
Performance


1
pr-performance
1 commits created
lines: + 58, - 12
58 lines added
12 lines deleted


nikitamikhaylov
MEMBER
[11617] Parallel formatting

Created

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en Changelog category (leave one): - New Feature Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md): - parallel parsing was rewritten to processors - fixed the issue when array of JSONs can't be parsed in parallel (it is not a bugfix) - parallel formatting was implemented


Fast test
Functional stateless tests (debug)
Functional stateful tests (debug)
Split build smoke test
Functional stateful tests (thread)
Functional stateless tests (ubsan)
Functional stateless tests (thread)
Functional stateful tests (ubsan)
Stress test (thread)
Stress test (undefined)
Integration tests (asan)
Functional stateless tests (address)
Functional stateful tests (address)
Stress test (address)
Functional stateless tests (memory)
Functional stateful tests (memory)
Stress test (memory)
AST fuzzer


2
doc-alert
pr-feature
17 commits created
lines: + 988, - 127
988 lines added
127 lines deleted


marked as ready for review

robot-clickhouse
MEMBER
[13499] Release pull request for branch 20.7

Created

This PullRequest is part of ClickHouse release cycle. It's used by CI system only. Don't perform any changes with it.

Fast test
Performance
Functional stateful tests (release, DatabaseAtomic)
Unit tests UBSAN
Unit tests TSAN
Unit tests release clang
Unit tests release gcc
Style check
Unit tests ASAN
Unit tests MSAN
Docs check
ClickHouse special build check
PVS check
AST fuzzer
Push to dockerhub
Functional stateful tests (ubsan)
Split build smoke test
Functional stateful tests (debug)
Functional stateful tests (memory)
Functional stateful tests (address)
Functional stateful tests (thread)
Functional stateful tests (release)
Compatibility check
Marker check
ClickHouse build check
Testflows check
Functional stateless tests (ubsan)
Functional stateless tests (release, polymorphic parts enabled)
Functional stateless tests (release)
Functional stateless tests (release, DatabaseAtomic)
Functional stateless tests (address)
Functional stateless tests (memory)
Stress test (address)
Functional stateless tests (debug)
Functional stateless tests (thread)
Stress test (memory)
Integration tests (asan)
Integration tests (release)
Stress test (thread)

Stress test (undefined)

3
release
144 commits created
lines: + 3480, - 1148
3480 lines added
1148 lines deleted

robot-clickhouse
MEMBER
[14297] Release pull request for branch 20.8

Created

This PullRequest is part of ClickHouse release cycle. It's used by CI system only. Don't perform any changes with it.

Fast test
Performance
Functional stateful tests (release, DatabaseAtomic)
Unit tests UBSAN
Unit tests TSAN
Unit tests release clang
Unit tests release gcc
Style check
Unit tests ASAN
Unit tests MSAN
Docs check
ClickHouse special build check
PVS check
AST fuzzer
Push to dockerhub
Functional stateful tests (debug)
Split build smoke test
Functional stateful tests (thread)
Functional stateful tests (ubsan)
Functional stateful tests (address)
Compatibility check
Functional stateful tests (release)
Marker check
Functional stateful tests (memory)
Testflows check
Functional stateless tests (ubsan)
Functional stateless tests (release)
Functional stateless tests (release, polymorphic parts enabled)
Stress test (thread)
Stress test (address)
Functional stateless tests (release, DatabaseAtomic)
Stress test (undefined)
Functional stateless tests (address)
Stress test (memory)
Functional stateless tests (debug)
Functional stateless tests (memory)
ClickHouse build check
Functional stateless tests (thread)

Integration tests (asan)
Integration tests (release)


6
release
88 commits created
lines: + 1868, - 535
1868 lines added
535 lines deleted

robot-clickhouse
MEMBER
[14587] Release pull request for branch 20.9

Created

This PullRequest is part of ClickHouse release cycle. It's used by CI system only. Don't perform any changes with it.

Fast test
Performance
Functional stateful tests (release, DatabaseAtomic)
Unit tests UBSAN
Unit tests TSAN
Unit tests release clang
Unit tests release gcc
Style check
Unit tests ASAN
Unit tests MSAN
Docs check
ClickHouse special build check
PVS check
AST fuzzer
Push to dockerhub
Split build smoke test
Functional stateful tests (debug)
Functional stateful tests (ubsan)
Functional stateful tests (address)
Functional stateful tests (thread)
Functional stateless tests (ubsan)
Functional stateful tests (memory)
Stress test (address)
Stress test (thread)
Stress test (undefined)
Functional stateless tests (address)
Compatibility check
Functional stateful tests (release)
Marker check
Stress test (memory)
Testflows check
Functional stateless tests (debug)
Functional stateless tests (release, polymorphic parts enabled)
Functional stateless tests (release, DatabaseAtomic)
Functional stateless tests (release)
Functional stateless tests (memory)
Functional stateless tests (thread)

Integration tests (release)
Integration tests (asan)
ClickHouse build check


1
release
56 commits created
lines: + 1398, - 383
1398 lines added
383 lines deleted

nikitamikhaylov
MEMBER
[15110] Splitting test_dictionaries_all_layouts_and_sources

Created

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en Changelog category (leave one): - Build/Testing/Packaging Improvement Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md): Splitted huge test `test_dictionaries_all_layouts_and_sources` into smaller ones.

Description check
Style check
Push to dockerhub
Docs check
Fast test
Yandex third-party checks (only for Yandex employees)
Functional stateful tests (debug)
Unit tests TSAN
Unit tests UBSAN
Unit tests release gcc
Compatibility check
Functional stateful tests (release, DatabaseAtomic)
Functional stateful tests (release)
Functional stateful tests (ubsan)
Functional stateful tests (thread)
Unit tests ASAN
PVS check
Split build smoke test
Functional stateful tests (address)
Unit tests MSAN
ClickHouse build check
Functional stateful tests (memory)
Testflows check
Marker check
Functional stateless tests (release, polymorphic parts enabled)
Functional stateless tests (release)
Functional stateless tests (ubsan)
ClickHouse special build check
Stress test (address)
Functional stateless tests (address)
AST fuzzer
Functional stateless tests (memory)
Functional stateless tests (debug)
Integration tests (release)
Performance
Integration tests (asan)


1
pr-build
6 commits created
lines: + 1141, - 351
1141 lines added
351 lines deleted

alekseik1
[15244] do not expose ClickHouse server until initialization is complete

Created

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en Changelog category (leave one): - Improvement Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md): Do not allow connections to ClickHouse server until all scripts in `/docker-entrypoint-initdb.d/` are executed. Detailed description / Documentation draft: As mentioned in #10963, docker container is expected to start accepting connections only after all init scripts are finished. Currently, the first startup of the server (which is done only for scripts execution) permits connections, thus making healthcheck scripts (like [wait-for-it.sh](https://github.com/vishnubob/wait-for-it)) trigger. This may result in incorrect behaviour of the latter. Closes #10963

Marker check

pr-improvement
1 commits created
lines: + 2, - 1
2 lines added
1 lines deleted

added a label

tavplubix
MEMBER
[15243] Try fix race on Context::settings

Created

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en Changelog category (leave one): - Bug Fix Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md): Not for changelog https://clickhouse-test-reports.s3.yandex.net/0/dfcc55b578d9e190657d2f3e8d0d34dce474d0fa/stress_test_(thread)/stderr.log

Description check
Docs check
Style check
Push to dockerhub
Fast test
PVS check
Split build smoke test
Functional stateful tests (debug)
Yandex third-party checks (only for Yandex employees)
Compatibility check
Functional stateful tests (release)
Unit tests ASAN
Functional stateful tests (ubsan)
Unit tests release gcc
Functional stateful tests (release, DatabaseAtomic)
Unit tests UBSAN
Unit tests TSAN
Functional stateful tests (address)
Unit tests MSAN
Functional stateful tests (thread)
Testflows check
Functional stateful tests (memory)
ClickHouse build check
Marker check
Functional stateless tests (release, polymorphic parts enabled)
ClickHouse special build check
Functional stateless tests (ubsan)
Stress test (address)
Stress test (undefined)
Functional stateless tests (address)
Functional stateless tests (memory)
Functional stateless tests (debug)
Integration tests (release)
Performance
Functional stateless tests (thread)
Integration tests (asan)


pr-bugfix
2 commits created
lines: + 2, - 1
2 lines added
1 lines deleted

4ertus2
MEMBER
[15242] Fix JOIN with GROUP BY over StorageMerge

Created

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en Changelog category (leave one): - Bug Fix Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md): Fix 'Unknown identifier' in GROUP BY when query has JOIN over Merge table. Fixes #15228


PVS check
ClickHouse special build check
ClickHouse build check

Fast test
Marker check
Yandex synchronization check (only for Yandex employees)

pr-bugfix
1 commits created
lines: + 39, - 4
39 lines added
4 lines deleted

renamed

abyss7
CONTRIBUTOR
[11298] Describe and test ClickHouse grammar using ANTLR4 format

Created

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en Changelog category (leave one): - Improvement Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md): TODO!


Style check
PVS check
ClickHouse build check
ClickHouse special build check
Marker check
Yandex synchronization check (only for Yandex employees)
Yandex third-party checks (only for Yandex employees)

2
pr-improvement
submodule changed
91 commits created
lines: + 27778, - 981
27778 lines added
981 lines deleted

nikitamikhaylov
MEMBER
[14958] Refactor cache dictionary

Created

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en Changelog category (leave one): - Improvement Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md): * Completely eliminate callbacks and locks for acquiring them. * Keys are not divided into "not found" and "expired", but stored in the same map during query.



Style check
ClickHouse special build check
Stress test (thread)
Marker check

pr-improvement
6 commits created
lines: + 508, - 315
508 lines added
315 lines deleted

akuzm
MEMBER
[15144] Perf test: bind server to one NUMA node

Created

another try with disabled percpu arenas https://github.com/ClickHouse/ClickHouse/pull/12631#issuecomment-696655597 Changelog category (leave one): - Not for changelog (changelog entry is not required)

Description check
Style check
Push to dockerhub
Docs check
Fast test
Yandex synchronization check (only for Yandex employees)
Yandex third-party checks (only for Yandex employees)
PVS check
Split build smoke test
Functional stateful tests (debug)
Functional stateful tests (release, DatabaseAtomic)
Compatibility check
Unit tests ASAN
Unit tests release gcc
Functional stateful tests (ubsan)
Unit tests TSAN
Unit tests UBSAN
Integration tests (asan)
Integration tests (release)
Functional stateful tests (release)
Functional stateful tests (thread)
ClickHouse build check
Testflows check
Functional stateful tests (address)
Functional stateless tests (release, DatabaseAtomic)
Functional stateful tests (memory)
ClickHouse special build check
Functional stateless tests (ubsan)
Unit tests MSAN
Functional stateless tests (release, polymorphic parts enabled)
Stress test (address)
Stress test (undefined)
Stress test (thread)
Functional stateless tests (release)
Functional stateless tests (address)
Functional stateless tests (memory)
Stress test (memory)
Functional stateless tests (debug)
AST fuzzer
Functional stateless tests (thread)
Marker check

Performance

9
pr-not-for-changelog
submodule changed
17 commits created
lines: + 10, - 3
10 lines added
3 lines deleted


alesapin
MEMBER
[15236] Trying to split sequential and parallel functional tests

Created

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en Changelog category (leave one): - Build/Testing/Packaging Improvement Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md): Now we can run almost all stateless functional tests in parallel.

Description check
Style check
Push to dockerhub
Docs check
Fast test
Yandex synchronization check (only for Yandex employees)
Yandex third-party checks (only for Yandex employees)
PVS check
Split build smoke test
Functional stateful tests (debug)
Functional stateful tests (release, DatabaseAtomic)
Compatibility check
Unit tests ASAN
Unit tests release gcc
Functional stateful tests (release)
Functional stateful tests (ubsan)
Unit tests TSAN
Unit tests UBSAN
Functional stateful tests (address)
Unit tests MSAN
Functional stateful tests (thread)
ClickHouse build check
Functional stateful tests (memory)
Marker check
Testflows check
Functional stateless tests (release, polymorphic parts enabled)
Functional stateless tests (release)
ClickHouse special build check
Stress test (memory)
Stress test (thread)
Functional stateless tests (thread)
Stress test (address)
AST fuzzer
Performance
Integration tests (release)
Integration tests (asan)


2
pr-build
1 commits created
lines: + 94, - 10
94 lines added
10 lines deleted


Enmk
CONTRIBUTOR
[9404] Date time64 extended range

Created

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en Changelog category (leave one): - New Feature Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md): Extended range of DateTime64 to properly support dates from year 1698 to 2378. Improved support of DateTime around zero date (1970-01-01). ... Detailed description / Documentation draft: Extended range of `DateTime64` to support dates outside of years **1970-2105**. Introduced `TimeZoneImpl` class that is based on existing `DateLUTImpl`, loading new LUTs on-demand. Max range is limited in code by the number of LUTs that can be stored in a single TimeZone. Also, fixed `DateTimeImpl` to work correctly on the full range of time_t values (including negative ones) and fixed calculating hours/minutes/seconds around epoch start. ... Progress: - [X] Load LUT with custom `time_t` offset - [X] Manage dynamic LUTs in `TimeZoneImpl` - [X] Add tests that verify validity LUTs used by `TimeZoneImpl` - [x] Integrate `TimeZoneImpl` into functions working with `DateTime64` - [x] Cleanup - [ ] Add more high-level tests (⚠️ **Help needed** ⚠️) - [ ] Fix invalid values when crossing LUT borders with `addYear`, etc. functions. There are also open questions regarding the performance of dynamic LUT management in `TimeZoneImpl`. closes #7316


Marker check

Merge with master

2
altinity
can be tested
doc-alert
pr-feature
4 commits created
lines: + 2506, - 530
2506 lines added
530 lines deleted


unlabeled



akuzm
MEMBER
[15230] debug perf test run time

Created

Changelog category (leave one): - Not for changelog (changelog entry is not required)

Description check
Push to dockerhub
Style check
Fast test
Yandex synchronization check (only for Yandex employees)
Yandex third-party checks (only for Yandex employees)
Docs check
PVS check
Split build smoke test
Functional stateful tests (debug)
Integration tests (release)
Compatibility check
Functional stateful tests (release, DatabaseAtomic)
Unit tests ASAN
Integration tests (asan)
Functional stateful tests (ubsan)
Unit tests release gcc
Functional stateful tests (address)
Unit tests TSAN
Functional stateful tests (thread)
Unit tests UBSAN
Unit tests MSAN
Functional stateful tests (release)
ClickHouse build check
Functional stateful tests (memory)
Testflows check
Functional stateless tests (release, DatabaseAtomic)
Functional stateless tests (release, polymorphic parts enabled)
Functional stateless tests (release)
ClickHouse special build check
Functional stateless tests (ubsan)
Stress test (address)
Stress test (undefined)
Stress test (memory)
Functional stateless tests (address)
AST fuzzer
Marker check
Functional stateless tests (memory)
Functional stateless tests (debug)
Functional stateless tests (thread)
Stress test (thread)

Performance

pr-not-for-changelog
1 commits created
lines: + 79, - 7
79 lines added
7 lines deleted

assigned

amosbird
MEMBER
[15220] Fix joinGet crash with LowCardinality types

Created

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en Changelog category (leave one): - Bug Fix Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md): Fix instance crash when using joinGet with LowCardinality types. This fixes https://github.com/ClickHouse/ClickHouse/issues/15214 Detailed description / Documentation draft: Null.

Description check
Docs check
Style check
Push to dockerhub
Fast test
Yandex synchronization check (only for Yandex employees)
Yandex third-party checks (only for Yandex employees)
PVS check
Functional stateful tests (debug)
Integration tests (release)
Functional stateful tests (ubsan)
Functional stateful tests (release, DatabaseAtomic)
Integration tests (asan)
Functional stateful tests (release)
Functional stateful tests (thread)
Functional stateful tests (address)
ClickHouse build check
Functional stateful tests (memory)
Unit tests ASAN
Unit tests MSAN
Functional stateless tests (release, polymorphic parts enabled)
Unit tests TSAN
Unit tests release gcc
Functional stateless tests (ubsan)
Functional stateless tests (release, DatabaseAtomic)
Functional stateless tests (release)
Compatibility check
ClickHouse special build check
Unit tests UBSAN
Split build smoke test
Stress test (memory)
Functional stateless tests (address)
Stress test (address)
Functional stateless tests (memory)
Testflows check
Functional stateless tests (debug)
Stress test (undefined)
Functional stateless tests (thread)
Marker check
Performance

Stress test (thread)
AST fuzzer

1
pr-bugfix
1 commits created
lines: + 8, - 1
8 lines added
1 lines deleted

assigned

fastio
CONTRIBUTOR
[15191] Avoid to commit empty parts to storage

Created

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en Changelog category (leave one): - Improvement Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md): Avoid to commit empty parts to storage in background. Detailed description / Documentation draft: As #15180 mentioned, the outdated parts were removed in the background. The expired parts were replaced by empty parts with commited state, which generated in the merge phase. If the generated part is empty, avoid to commit it to storage, but remove the outdated parts.



Fast test
Marker check
Yandex synchronization check (only for Yandex employees)

5
can be tested
pr-improvement
2 commits created
lines: + 112, - 19
112 lines added
19 lines deleted

robot-clickhouse
MEMBER
[15140] Backport #15088 to 20.7: Keep LowCardinality in MergeJoin left key result type

Created

Original pull-request #15088 Cherry-pick pull-request #15133 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.

Fast test
Performance
Functional stateful tests (release, DatabaseAtomic)
Style check
Unit tests UBSAN
Unit tests MSAN
Unit tests release clang
Unit tests ASAN
Unit tests TSAN
Unit tests release gcc
ClickHouse special build check
Docs check
AST fuzzer
PVS check
Push to dockerhub
Compatibility check
Functional stateful tests (release)
Functional stateful tests (ubsan)
Functional stateful tests (address)
Functional stateful tests (memory)
Functional stateful tests (thread)
Functional stateful tests (debug)
ClickHouse build check
Functional stateless tests (release)
Split build smoke test
Functional stateless tests (release, polymorphic parts enabled)
Functional stateless tests (release, DatabaseAtomic)
Functional stateless tests (ubsan)
Testflows check
Functional stateless tests (address)
Functional stateless tests (memory)
Functional stateless tests (debug)
Stress test (address)
Functional stateless tests (thread)
Integration tests (release)
Stress test (memory)
Integration tests (asan)
Stress test (thread)

Marker check

Stress test (undefined)

1
pr-backport
2 commits created
lines: + 195, - 4
195 lines added
4 lines deleted

robot-clickhouse
MEMBER
[15143] Backport #15088 to 20.6: Keep LowCardinality in MergeJoin left key result type

Created

Original pull-request #15088 Cherry-pick pull-request #15131 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.

Fast test
Performance
Functional stateful tests (release, DatabaseAtomic)
Unit tests UBSAN
Style check
Unit tests TSAN
Unit tests ASAN
Unit tests MSAN
Unit tests release gcc
Unit tests release clang
Docs check
PVS check
AST fuzzer
ClickHouse special build check
Push to dockerhub
Functional stateful tests (ubsan)
Functional stateful tests (release)
Functional stateful tests (address)
Functional stateful tests (memory)
Functional stateful tests (debug)
Functional stateful tests (thread)
Compatibility check
ClickHouse build check
Functional stateless tests (release)
Functional stateless tests (release, DatabaseAtomic)
Functional stateless tests (release, polymorphic parts enabled)
Functional stateless tests (ubsan)
Split build smoke test
Testflows check
Functional stateless tests (address)
Functional stateless tests (memory)
Stress test (undefined)
Functional stateless tests (debug)
Stress test (address)
Functional stateless tests (thread)
Integration tests (release)
Stress test (memory)
Integration tests (asan)
Stress test (thread)

Marker check


1
pr-backport
2 commits created
lines: + 195, - 4
195 lines added
4 lines deleted

CurtizJ
MEMBER
[15226] Try enable randomization of part type in tests

Created

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en Changelog category (leave one): - Build/Testing/Packaging Improvement Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md): Now type of part will be randomized between wide and compact to cover more cases without running all tests twice.


Functional stateless tests (debug)
Functional stateless tests (thread)
Functional stateless tests (address)
Functional stateless tests (ubsan)
Functional stateless tests (memory)
Stress test (memory)
Stress test (thread)
Stress test (address)
Stress test (undefined)
Performance


pr-build
1 commits created
lines: + 2, - 4
2 lines added
4 lines deleted

added a label

robot-clickhouse
MEMBER
[15224] Backport #15192 to 20.9: Fix insert into storage Buffer after alter.

Created

Original pull-request #15192 Cherry-pick pull-request #15218 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.

Fast test
Performance
Functional stateful tests (release, DatabaseAtomic)
Unit tests UBSAN
Unit tests ASAN
Unit tests release clang
Unit tests TSAN
Unit tests MSAN
Style check
Unit tests release gcc
ClickHouse special build check
Docs check
PVS check
AST fuzzer
Push to dockerhub
Functional stateful tests (debug)
Functional stateful tests (address)
Functional stateful tests (thread)
Functional stateful tests (ubsan)
Functional stateful tests (memory)
Functional stateful tests (release)
Functional stateless tests (ubsan)
Compatibility check
ClickHouse build check
Split build smoke test
Stress test (thread)
Functional stateless tests (address)
Stress test (memory)
Functional stateless tests (debug)
Stress test (address)
Functional stateless tests (release)
Stress test (undefined)
Functional stateless tests (release, polymorphic parts enabled)
Functional stateless tests (release, DatabaseAtomic)
Testflows check
Functional stateless tests (memory)
Functional stateless tests (thread)
Integration tests (asan)

Marker check

Integration tests (release)

pr-backport
1 commits created
lines: + 39, - 8
39 lines added
8 lines deleted

added a label

robot-clickhouse
MEMBER
[15223] Backport #15192 to 20.6: Fix insert into storage Buffer after alter.

Created

Original pull-request #15192 Cherry-pick pull-request #15219 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.

Fast test
Performance
Functional stateful tests (release, DatabaseAtomic)
Unit tests UBSAN
Unit tests ASAN
Unit tests release clang
Unit tests TSAN
Unit tests MSAN
Style check
Unit tests release gcc
ClickHouse special build check
Docs check
PVS check
AST fuzzer
Push to dockerhub
Split build smoke test
Compatibility check
Functional stateful tests (debug)
Testflows check
Functional stateful tests (thread)
Functional stateful tests (ubsan)
Functional stateful tests (release)
ClickHouse build check
Functional stateful tests (address)
Functional stateless tests (release, DatabaseAtomic)
Functional stateful tests (memory)
Functional stateless tests (release, polymorphic parts enabled)
Functional stateless tests (ubsan)
Functional stateless tests (release)
Functional stateless tests (address)
Functional stateless tests (debug)
Functional stateless tests (memory)
Functional stateless tests (thread)
Stress test (address)
Stress test (undefined)
Stress test (thread)
Stress test (memory)
Integration tests (asan)

Marker check

Integration tests (release)

pr-backport
1 commits created
lines: + 39, - 8
39 lines added
8 lines deleted

added a label

robot-clickhouse
MEMBER
[15222] Backport #15192 to 20.8: Fix insert into storage Buffer after alter.

Created

Original pull-request #15192 Cherry-pick pull-request #15216 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.

Fast test
Performance
Functional stateful tests (release, DatabaseAtomic)
Unit tests UBSAN
Unit tests ASAN
Unit tests release clang
Unit tests TSAN
Unit tests MSAN
Style check
Unit tests release gcc
ClickHouse special build check
Docs check
PVS check
AST fuzzer
Push to dockerhub
Split build smoke test
Functional stateful tests (debug)
Functional stateful tests (ubsan)
Functional stateful tests (thread)
Functional stateful tests (release)
Functional stateful tests (address)
Functional stateful tests (memory)
ClickHouse build check
Functional stateless tests (release, DatabaseAtomic)
Functional stateless tests (release, polymorphic parts enabled)
Functional stateless tests (release)
Functional stateless tests (ubsan)
Compatibility check
Functional stateless tests (address)
Stress test (memory)
Stress test (thread)
Stress test (address)
Testflows check
Functional stateless tests (memory)
Stress test (undefined)
Functional stateless tests (debug)
Integration tests (release)
Functional stateless tests (thread)
Integration tests (asan)

Marker check


pr-backport
1 commits created
lines: + 39, - 8
39 lines added
8 lines deleted

added a label

robot-clickhouse
MEMBER
[15221] Backport #15192 to 20.7: Fix insert into storage Buffer after alter.

Created

Original pull-request #15192 Cherry-pick pull-request #15217 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.