Skip to content

[CI] Restrict LTS coverage tracking to the checkout #645

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
michel2323 merged 1 commit into from
Sep 25, 2026
Merged

[CI] Restrict LTS coverage tracking to the checkout #645

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions .gitlab-ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -141,8 +141,11 @@ stages: [build, test, coverage]
# Base.julia_cmd().
# --code-coverage propagates to the parallel workers via Base.julia_cmd(), as the
# cpu-target does (see ci.yml). Every LTS-gated branch is unreachable on the rolling
# stack, so this job is the only coverage signal for those paths.
- julia -C "$JULIA_JIT_TARGET" --code-coverage=user --color=yes --project=test test/runtests.jl --quickfail
# stack, so this job is the only coverage signal for those paths. Track only the
# checkout: `user` also covers every dependency, so each of the ~45 workers writes
# thousands of .cov files into the depot on flare, which stretches worker start-up
# and shutdown past Malt's fixed 30 s / 20 s timeouts and fails the run.
- julia -C "$JULIA_JIT_TARGET" --code-coverage=@$CI_PROJECT_DIR --color=yes --project=test test/runtests.jl --quickfail
# Collapse the per-file .cov output into lcov.info for the upload job; directories
# match the buildkite julia-coverage plugin's.
- julia --color=yes --project=$JULIA_DEPOT_PATH/environments/coverage -e '
Expand Down
Loading