ci: improve CI stability with parallel builds, Valgrind, and coverage
Some checks failed
CI Code / Check spelling (pull_request) Successful in 22s
CI Code / Check coding style (pull_request) Successful in 35s
CI Code / Code Coverage (pull_request) Successful in 1m45s
CI Code / Linux (debian) (pull_request) Failing after 5m46s
CI Code / Linux (ubuntu) (pull_request) Failing after 7m50s
CI Code / Linux (arch) (pull_request) Failing after 9m10s

This commit is contained in:
2026-01-28 19:35:22 +03:00
parent 8353a29b4f
commit 01c100a60b
7 changed files with 272 additions and 55 deletions

View File

@@ -90,6 +90,15 @@ set -e
```
This will run the same tests that the CI runs and refuse the push if it fails.
The CI script runs 4 parallel builds with different configurations, each with Valgrind and functional tests.
Build 1 also collects code coverage (lines, functions, branches).
Output shows test results per build:
```
✓ Build 1 passed (unit: 437/0, func: 69/0, cov: L:27.5% F:36.2% B:18.1%, 5m39s)
✓ Build 2 passed (unit: 398/0, func: 69/0, 5m00s)
```
Note that it will run on the actual content of the repository directory and not
what may have been staged/committed.