CI: run integration suite nightly (08:00 UTC)#397
Merged
Conversation
Add a schedule: trigger to integration.yml so the slow statistical-recovery tests run automatically every night against master, not just on manual dispatch. The fast tests already run on every push/PR; the slow tier was the one at risk of silently rotting since nothing triggered it. cron '0 8 * * *' = 08:00 UTC, ~02:00 Denver (MDT) / ~01:00 (MST); GitHub cron is fixed UTC with no DST adjustment. workflow_dispatch is retained for ad-hoc runs. py3.12 only (slow tests are pure-Python numerics).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a
schedule:trigger tointegration.ymlso the slow statistical-recovery tests run nightly againstmaster, not only on manual dispatch.0 8 * * *— 08:00 UTC, ≈02:00 Denver in summer (MDT) / ≈01:00 in winter (MST). GitHub cron is fixed UTC, so it drifts an hour across the DST switch; either way it's the middle of the night.pytest -m slow -n auto, py3.12 only (the slow tests are pure-Python numerics; the per-PRtestsjob keeps the py3.10/py3.12 matrix).workflow_dispatchis retained for ad-hoc runs.Note: the nightly selects
-m slow, so future integration tests should carry@pytest.mark.slowto be included.Scheduled runs only fire from the default branch, so the cron activates once this merges; I'll manual-dispatch post-merge to confirm the workflow is still valid.