Skip to content

ci(coverage): run the coverage job weekly and on request, not on every push - #217

Closed
MaartenMarsman wants to merge 1 commit into
developfrom
ci/coverage-weekly
Closed

MaartenMarsman wants to merge 1 commit into
developfrom
ci/coverage-weekly

Conversation

@MaartenMarsman

Copy link
Copy Markdown
Collaborator

Every coverage run since 2026-10-21 09:00 has ended 38-75 minutes in with the hosted runner being recycled ("The runner has received a shutdown signal"), one failure email per push and per pull request; none reached a test failure. Under covr the every-run tier takes about an hour on the 2-core runner.

Change: the job runs on a weekly schedule (Sundays 06:00 UTC, on develop, after the weekly certification) and on manual dispatch, with a 90-minute timeout. No package or test changes. Per-push testing stays with fast-checks.yaml and R-CMD-check.yaml.

The cause of the runner shutdowns (most likely memory under instrumentation) is not addressed here; it belongs with the test-suite work (backlog item 47).

…y push

Under covr the every-run tier takes about an hour on the 2-core runner.
Since 2026-10-21 09:00 every push-triggered coverage run has ended with
the hosted runner being recycled mid-job ("runner has received a shutdown
signal"), one failure email per push and per pull request. The job now
runs Sundays at 06:00 UTC on develop and on manual dispatch, with a
90-minute timeout. fast-checks.yaml and R-CMD-check.yaml remain the
per-push test jobs.
@MaartenMarsman
MaartenMarsman deleted the ci/coverage-weekly branch October 21, 2026 17:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant