ci: improve CI stability with parallel builds, Valgrind, and coverage
All checks were successful
CI Code / Check spelling (pull_request) Successful in 18s
CI Code / Check coding style (pull_request) Successful in 33s
CI Code / Linux (debian) (pull_request) Successful in 6m48s
CI Code / Linux (ubuntu) (pull_request) Successful in 6m57s
CI Code / Linux (arch) (pull_request) Successful in 12m4s
CI Code / Code Coverage (pull_request) Successful in 15m24s
All checks were successful
CI Code / Check spelling (pull_request) Successful in 18s
CI Code / Check coding style (pull_request) Successful in 33s
CI Code / Linux (debian) (pull_request) Successful in 6m48s
CI Code / Linux (ubuntu) (pull_request) Successful in 6m57s
CI Code / Linux (arch) (pull_request) Successful in 12m4s
CI Code / Code Coverage (pull_request) Successful in 15m24s
This commit is contained in:
@@ -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.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user