Repository navigation
ci: activate v3 storage schedule runs from main (#760) - #787
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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
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.
GitHub starts scheduled workflows from the default branch. This adds the identical
deterministic-schedules.ymlfrom #786 to main so nightly/manual runs can explicitly check out v3 and exercise its bounded storage schedule suite.Merge after #786 lands on v3. This is intentionally workflow-only: v2.x gets no Shuttle dependency or test implementation. PR checks target v3; the scheduled and default manual source ref is v3. Update those refs to main at the v3 release cut.
The workflow runs Linux/macOS/Windows stable and Linux Rust 1.89, bounds the execution budget, rejects zero selected tests, and uploads source, lockfile, compiler details and failure logs for replay. It requires only contents-read permission and does not change branch protection or create issues/comments.
Validation: byte-identical to the workflow in #786; actionlint 1.7.12 passed. Its actual exploration shell block passed PR/nightly budgets on the bench under Rust 1.89, rejected a non-instrumented zero-test build, and retained the injected failure's status and replay schedule through tee. Native matrix results are tracked on #786.
Companion to #786; part of #760 / #383.