mirror of
https://github.com/ClickHouse/ClickHouse.git
synced 2024-10-06 16:40:48 +00:00
updates 3
This commit is contained in:
parent
237d4c1c68
commit
c44bb6a009
68
CI.md
68
CI.md
@ -5,35 +5,36 @@
|
|||||||
- Runs only on PRs.
|
- Runs only on PRs.
|
||||||
- Checks if the PR can be successfully merged with the master branch.
|
- Checks if the PR can be successfully merged with the master branch.
|
||||||
- Not present in the checks list if there are no conflicts.
|
- Not present in the checks list if there are no conflicts.
|
||||||
- Status if the conflicts are present: "Cannot fetch mergecommit".
|
- Status if the conflicts are present: `Cannot fetch mergecommit`.
|
||||||
1. [Docs check](#docs-check)
|
1. [Docs check](#docs-check)
|
||||||
- Tries to build the ClickHouse's documentation website.
|
- Tries to build the ClickHouse's documentation website.
|
||||||
- Checks the inner cross-links status.
|
- Checks the inner cross-links status.
|
||||||
2. Description check
|
2. Description check
|
||||||
- Run only on PRs.
|
- Run only on PRs.
|
||||||
- Check the conformance of the PR's description with the PULL_REQUEST_TEMPLATE.md
|
- Check the conformance of the PR's description with the [PULL_REQUEST_TEMPLATE.md](https://github.com/yandex/ClickHouse/blob/master/.github/PULL_REQUEST_TEMPLATE.md).
|
||||||
3. Push to dockerhub
|
3. Push to dockerhub
|
||||||
- Checks differences between the ClickHouse's current DockerHub image.
|
- Checks differences between the ClickHouse's current DockerHub image.
|
||||||
- Status on success "nothing to update" or "successfully updated".
|
- Status on success "nothing to update" or "successfully updated".
|
||||||
4. Marker check
|
4. Marker check
|
||||||
- Checks that all CI's check have been initiated.
|
- Checks that all CI's check have been initiated.
|
||||||
- Success status: "All checks were started".
|
- Status on success: `All checks were started`.
|
||||||
5. [Style check](#style-check)
|
5. [Style check](#style-check)
|
||||||
- Checks the code style according to `utils/check-style/check-style`.
|
- Checks the code style according to `utils/check-style/check-style` binary.
|
||||||
- Status on success: "Style check passed".
|
- Status on success: `Style check passed`.
|
||||||
6. PVS check
|
6. [PVS check](#pvs-check)
|
||||||
- Static analysis tool, checks code with PVS-studio.
|
- Static analysis tool, checks code with PVS-studio.
|
||||||
7. Fast test
|
7. [Fast test](#fast-test)
|
||||||
- First executable check.
|
- First executable check.
|
||||||
- Builds a subset of ClickHouse's code (without embedded compiler, ZooKeeper, etc.).
|
- Builds a subset of ClickHouse's code (without embedded compiler, ZooKeeper, etc.).
|
||||||
- Runs a subset of tests (functional, stateless, stateful, and integration ones).
|
- Runs a subset of tests (functional, stateless, stateful, and integration ones).
|
||||||
- Blocks the start of Build check on errors.
|
- Blocks the start of Build check on errors.
|
||||||
- Intended to detect some errors and limit the CI run time on broken commits.
|
- Intended to detect some errors and limit the CI run time on broken commits.
|
||||||
|
- Success status: `fail: 0, passed: 1944, skipped: 229` (may differ).
|
||||||
8. Build check
|
8. Build check
|
||||||
- Build ClickHouse with various compilers (gcc-9, clang-10) and various sanitizers:
|
- Build ClickHouse with various compilers (gcc-9, clang-10) and various sanitizers: undefined (UBSan),
|
||||||
undfined (UBSan), address (ASan), memory (MSan), and thread (TSan).
|
address (ASan), memory (MSan), and thread (TSan).
|
||||||
9. Special build check
|
9. Special build check
|
||||||
- Checks the code with `clang-tidy`
|
- Checks the code with `clang-tidy`.
|
||||||
10. Compatibility check
|
10. Compatibility check
|
||||||
- Checks that `clickhouse` binary runs on distros with old libc versions.
|
- Checks that `clickhouse` binary runs on distros with old libc versions.
|
||||||
11. AST fuzzer
|
11. AST fuzzer
|
||||||
@ -44,12 +45,49 @@
|
|||||||
16. Split build smoke test
|
16. Split build smoke test
|
||||||
17. Testflows check
|
17. Testflows check
|
||||||
18. Performance tests.
|
18. Performance tests.
|
||||||
|
- Intended to measure the queries' relative and absolute performance changes.
|
||||||
|
- The longest check: takes about 5 hours to run.
|
||||||
|
|
||||||
### <a name="docs-check"></a> Docs check
|
### <a id="docs-check"></a> Docs check
|
||||||
- [Status page example](https://clickhouse-test-reports.s3.yandex.net/12550/eabcc293eb02214caa6826b7c15f101643f67a6b/docs_check.html)
|
- [Status page example](https://clickhouse-test-reports.s3.yandex.net/12550/eabcc293eb02214caa6826b7c15f101643f67a6b/docs_check.html)
|
||||||
- `docs_output.txt` contains the building log. [Successful result example](https://clickhouse-test-reports.s3.yandex.net/12550/eabcc293eb02214caa6826b7c15f101643f67a6b/docs_check/docs_output.txt)
|
- `docs_output.txt` contains the building log. [Successful result example](https://clickhouse-test-reports.s3.yandex.net/12550/eabcc293eb02214caa6826b7c15f101643f67a6b/docs_check/docs_output.txt)
|
||||||
|
### <a id="style-check"></a> Style check
|
||||||
### <a name="style-check"></a> Style check
|
|
||||||
- [Status page example](https://clickhouse-test-reports.s3.yandex.net/12550/659c78c7abb56141723af6a81bfae39335aa8cb2/style_check.html)
|
- [Status page example](https://clickhouse-test-reports.s3.yandex.net/12550/659c78c7abb56141723af6a81bfae39335aa8cb2/style_check.html)
|
||||||
- `output.txt` contains the check resulting errors (invalid tabulation etc), blank page means no errors. [Succesful
|
- `output.txt` contains the check resulting errors (invalid tabulation etc), blank page means no errors. [Successful result example](https://clickhouse-test-reports.s3.yandex.net/12550/659c78c7abb56141723af6a81bfae39335aa8cb2/style_check/output.txt).
|
||||||
result example](https://clickhouse-test-reports.s3.yandex.net/12550/659c78c7abb56141723af6a81bfae39335aa8cb2/style_check/output.txt)
|
|
||||||
|
### <a id="pvs-check"></a> PVS check
|
||||||
|
- [Status page example](https://clickhouse-test-reports.s3.yandex.net/12550/67d716b5cc3987801996c31a67b31bf141bc3486/pvs_check.html)
|
||||||
|
- `test_run.txt.out.log` contains the building and analyzing log file. It includes only parsing or not-found errors.
|
||||||
|
- `HTML report` contains the analysis results. For its description visit PVS's [official site](https://www.viva64.com/en/m/0036/#ID14E9A2B2CD).
|
||||||
|
|
||||||
|
### <a id="fast-test"></a> Fast test
|
||||||
|
[Status page example](https://clickhouse-test-reports.s3.yandex.net/12550/67d716b5cc3987801996c31a67b31bf141bc3486/fast_test.html)
|
||||||
|
|
||||||
|
#### Status page files
|
||||||
|
- `runlog.out.log` is the general log that includes all other logs.
|
||||||
|
- `test_log.txt`
|
||||||
|
- `submodule_log.txt` contains the messages about cloning and checkouting needed submodules.
|
||||||
|
- `stderr.log`
|
||||||
|
- `stdout.log`
|
||||||
|
- `clickhouse-server.log`
|
||||||
|
- `clone_log.txt`
|
||||||
|
- `install_log.txt`
|
||||||
|
- `clickhouse-server.err.log`
|
||||||
|
- `build_log.txt`
|
||||||
|
- `cmake_log.txt` contains messages about the C/C++ and Linux flags check.
|
||||||
|
|
||||||
|
#### Status page columns:
|
||||||
|
|
||||||
|
- *Test name* contains the name of the test (without the path e.g. all types of tests will be stripped to the name).
|
||||||
|
- *Test status* -- one of _Skipped_, _Success_, or _Fail_.
|
||||||
|
- *Test time, sec.* -- empty on this test.
|
||||||
|
|
||||||
|
## Where the tests are run
|
||||||
|
|
||||||
|
Intel Gold with 100500ZB RAM.
|
||||||
|
|
||||||
|
## QA
|
||||||
|
|
||||||
|
> What is a `Task (private network)` item on status pages?
|
||||||
|
|
||||||
|
It's a link to the Yandex's internal job system. Yandex guys can see the check's start time and its more verbose status.
|
||||||
|
Loading…
Reference in New Issue
Block a user