can you check if 01149_zookeeper_mutation_stuck_after_replace_partition failure is related?

can you check if 01149_zookeeper_mutation_stuck_after_replace_partition failure is related?

Cannot reproduce with local unsan build. It doesn't seem to be related though.

Error like Part 20210419_0_5263_999999999 intersects previous part 20210419_0_3820_6_5263 is reproducible in CI: https://clickhouse-test-reports.s3.yandex.net/23327/a035df3fc5252cd819ac195ab5edd55b2093fa12/stress_test_(address).html#fail1
Log: https://gist.github.com/tavplubix/7fab87c430c1e3891a3806aedd770f8f
I think now I understand how does it happen

As for 01149_zookeeper_mutation_stuck_after_replace_partition, it looks strange (https://gist.github.com/tavplubix/2f574958ed558a132e6df6405a5f631f), but does not seem to be related

ClickHouse special build check - build is ok, but Command 'docker run ... ' returned non-zero exit status 1, looks unrelated

Functional stateless tests (ANTLR debug) - 01155_old_mutation_parts_to_do - Can't parse input: no viable alternative at input 'modifysetting' - looks like ALTER ... SETTINGS is not implemented in ANTLR parser, I will add it to skip list, cc: @abyss7

Functional stateless tests (release, DatabaseReplicated) - Watching task ... is executing longer - known bug in DatabaseReplicatedDDLWorker::enqueueQuery, I will fix it

Functional stateless tests flaky check (address) - 01414_mutations_and_errors - Exception happened during execution of mutation 'mutation_4.txt' with part '20191002_2_2_0' reason: 'Code: 236, e.displayText() = DB::Exception: Cancelled mutating parts (version 21.7.1.6946)'. This error maybe retryable or not. In case of unretryable error, mutation can be killed with KILL MUTATION query. - But test is not modified, so it was flaky earlier

Stress test (thread) - ALTER TABLE sticking_mutations - looks suspicious, but there are many messages like Not enough idle threads to apply mutations at the moment in server log, so it's probably not related

Waiting for integration tests

@tavplubix "ClickHouse special build check 4/5 builds" is

2021-05-26 08:29:17 /build/obj-x86_64-linux-gnu/../src/Storages/MergeTree/ReplicatedMergeTreeQueue.cpp:271:5: error: use range-based for loop instead [modernize-loop-convert,-warnings-as-errors]
2021-05-26 08:29:17     for (auto it = in_partition->second.begin(); it != in_partition->second.end(); ++it)
2021-05-26 08:29:17     ^   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2021-05-26 08:29:17         (auto & it : in_partition->second)
2021-05-26 08:29:17 100814 warnings generated.
2021-05-26 08:29:17 Suppressed 100815 warnings (100812 in non-user code, 2 NOLINT, 1 with check filters).
2021-05-26 08:29:17 Use -header-filter=.* to display errors from all non-system headers. Use -system-headers to display errors from system headers as well.
2021-05-26 08:29:17 1 warning treated as error

It is now red in master

21.3 LTS ?