mirror of
https://github.com/checkpoint-restore/criu.git
synced 2026-07-17 16:47:50 +00:00
ci: stabilize gcov-test coverage upload
Two problems made gcov-test unreliable: 1. The gcov step ran with --max-procs 4, causing multiple gcov processes to concurrently read and update the same .gcda files. GCC does not protect these files against concurrent access, so this can silently corrupt coverage data or produce non-deterministic failures. Drop --max-procs to serialize gcov. 2. 'make codecov' curls the uploader binary from https://uploader.codecov.io/latest/linux/codecov at job runtime. This fails on Codecov CDN outages and on pull requests from forks where CODECOV_TOKEN is not forwarded. Replace this step with the pinned codecov/codecov-action@v5, which avoids the runtime curl and handles both authenticated and unauthenticated cases gracefully. Fixes: #2911 Signed-off-by: Ahmed Elaidy <elaidya225@gmail.com>
This commit is contained in:
parent
bcd66dc302
commit
e6bea0372b
2 changed files with 8 additions and 3 deletions
|
|
@ -195,6 +195,9 @@ fi
|
|||
# umask has to be called before a first criu run, so that .gcda (coverage data)
|
||||
# files are created with read-write permissions for all.
|
||||
umask 0000
|
||||
# Also fix permissions on .gcda files already created during the build (owned
|
||||
# by root). Restored processes run as non-root and must be able to write them.
|
||||
find . -name '*.gcda' -exec chmod a+rw {} +
|
||||
./criu/criu check
|
||||
./criu/criu check --all || echo $?
|
||||
if [ "$UNAME_M" == "x86_64" ]; then
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue