Nikita Mikhaylov
Nikita Mikhaylov
**Integration tests (amd_asan, old analyzer, 1/6)** - https://github.com/ClickHouse/ClickHouse/issues/88931 **Integration tests (amd_asan, old analyzer, 3/6)** - https://github.com/ClickHouse/ClickHouse/issues/89758 **Upgrade check (amd_debug)** - https://github.com/ClickHouse/ClickHouse/issues/89220 **AST fuzzer (amd_debug)** - https://github.com/ClickHouse/ClickHouse/issues/84186
I have a case when running integration test multiple times found an issue in this PR https://github.com/ClickHouse/ClickHouse/pull/64183 Disabling it will be a pity (the issue instead will be reproduced in...
Please also take a look: https://github.com/ClickHouse/ClickHouse/pull/62364
What do we think about using LLDB instead of GDB?
Not the whole test suite was run, but at least we have green integration tests with ASAN and TSAN.
Unit tests: ``` /home/ubuntu/ClickHouse/ClickHouse/contrib/llvm-project/libcxx/include/vector:1490: assertion __n < size() failed: vector[] index out of boundsProcess 394430 stopped * thread #1, name = 'unit_tests_dbms', stop reason = signal SIGABRT frame #0: 0x00007ffff7ddc00b...
The error is related: https://s3.amazonaws.com/clickhouse-test-reports/70691/9e241a16cafe23d6a7dc19e20bb488aff73a914e/stateless_tests__tsan__s3_storage__[1_3]/stderr.log The data-race appears around newly added code https://github.com/ClickHouse/ClickHouse/pull/69862
As per this comment https://github.com/ClickHouse/ClickHouse/pull/69645#issuecomment-2429257187 I believe the issue is fixed.
`Upgrade check (debug)` - broken in master.
Should we do the same for Stress tests?