Move Miri CI to a daily cron job#6243
Merged
Merged
Conversation
Miri takes hours and rarely completes on a PR. Run it instead on a daily schedule like fuzz and kani. Use the same tool to produce an issue when it fails.
Contributor
Author
|
I set it to start at 10:00 UTC since Kani runs until about 2 then the Fuzz job starts at 5 and ends around 9. Previous successful runs of Miri on PRs took 5-6h. |
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
2 participants
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.
Miri takes hours and rarely completes on a PR, cancelled ones give a red x on the PR the same as a CI failure.
Run it instead on a daily schedule like fuzz and kani.
Use the same tool as used for fuzz and kani to produce an issue when it fails.
Closes #5883