mirror of
https://github.com/ClickHouse/ClickHouse.git
synced 2024-11-22 07:31:57 +00:00
dbfb448290
There is logic regarding which keeper binary use to start keeper cluster in an integration test There 2 options: (1) standalone keeper binary (expected binary name clickhouse-keeper) (2) clickhouse binary with keeper inside Fixed: - option (1) didn't work since docker_compose_keeper.yaml didn't create target clickhouse-keeper at all - if clickhouse-keeper existed, option (1) was taken but clickhouse-keeper could be just a link to clickhouse binary (the link is created always during build if cmake option BUILD_STANDALONE_KEEPER is OFF) |
||
---|---|---|
.. | ||
base | ||
codebrowser | ||
compatibility | ||
fasttest | ||
fuzzer | ||
integration | ||
keeper-jepsen | ||
performance-comparison | ||
split_build_smoke_test | ||
sqlancer | ||
stateful | ||
stateless | ||
stress | ||
style | ||
testflows/runner | ||
unit | ||
util | ||
README.md |
ClickHouse Test Docker Image
License
View license information for the software contained in this image.