thevar1able/ClickHouse
1
0
Fork 0
mirror of https://github.com/ClickHouse/ClickHouse.git synced 2024-11-22 23:52:03 +00:00
Code Issues Packages Projects Releases Wiki Activity

Bring back the strict check

Browse Source 
Also update the doc.
This commit is contained in:
Pablo Marcos 2024-07-31 12:09:49 +00:00
parent ba63bd1de7
commit 15e0033016
2 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
tests/integration/README.md
View File

@ -124,10 +124,11 @@ You can just open shell inside a container by overwritting the command:
### Parallel test execution ### Parallel test execution
On the CI, we run a number of parallel runners (5 at the time of this writing), each on its own On the CI, we run a number of parallel runners (5 at the time of this writing), each on its own
Docker container. These runner containers spawn more containers for the services needed such as Docker container. These runner containers spawn more containers for each test for the services
ZooKeeper, MySQL, PostgreSQL and minio, among others. Within each runner, tests are parallelized needed such as ZooKeeper, MySQL, PostgreSQL and minio, among others. This means that tests do not
using [pytest-xdist](https://pytest-xdist.readthedocs.io/en/stable/). We're using `--dist=loadfile` share any services among them. Within each runner, tests are parallelized using
to [distribute the load](https://pytest-xdist.readthedocs.io/en/stable/distribution.html). In the [pytest-xdist](https://pytest-xdist.readthedocs.io/en/stable/). We're using `--dist=loadfile` to
[distribute the load](https://pytest-xdist.readthedocs.io/en/stable/distribution.html). In the
documentation words: this guarantees that all tests in a file run in the same worker. This means documentation words: this guarantees that all tests in a file run in the same worker. This means
that any test within the same file will never execute their tests in parallel. They'll be executed that any test within the same file will never execute their tests in parallel. They'll be executed
on the same worker one after the other. on the same worker one after the other.

4
tests/integration/test_storage_s3_queue/test.py
View File

@ -907,7 +907,7 @@ def test_max_set_age(started_cluster):
file_with_error = f"max_set_age_fail_{uuid4().hex[:8]}.csv" file_with_error = f"max_set_age_fail_{uuid4().hex[:8]}.csv"
put_s3_file_content(started_cluster, f"{files_path}/{file_with_error}", values_csv) put_s3_file_content(started_cluster, f"{files_path}/{file_with_error}", values_csv)
wait_for_condition(lambda: failed_count + 1 <= get_object_storage_failures()) wait_for_condition(lambda: failed_count + 1 == get_object_storage_failures())
node.query("SYSTEM FLUSH LOGS") node.query("SYSTEM FLUSH LOGS")
assert "Cannot parse input" in node.query( assert "Cannot parse input" in node.query(
@ -920,7 +920,7 @@ def test_max_set_age(started_cluster):
) )
) )
wait_for_condition(lambda: failed_count + 2 <= get_object_storage_failures()) wait_for_condition(lambda: failed_count + 2 == get_object_storage_failures())
node.query("SYSTEM FLUSH LOGS") node.query("SYSTEM FLUSH LOGS")
assert "Cannot parse input" in node.query( assert "Cannot parse input" in node.query(