Try scheduling CI runs #298
Merged
Conversation
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
|
r? @therealprof (rust-highfive has picked a reviewer for you, use r? to override) |
rust-highfive
added
S-waiting-on-review
adamgreig
force-pushed
the
schedule-ci
branch
from
3f42ec3 to
cf49826
Compare
thalesfragoso
approved these changes
Dec 2, 2020
|
Build succeeded: |
bors bot
added a commit
that referenced
this pull request
Dec 8, 2020
305: Add required 'labels' field to scheduled CI, update next run date r=therealprof a=adamgreig See also #298. This should fail at 10pm today _and open an issue this time_, then we'll update it to remove the intentional failure and perhaps set the scheduled date to something more useful. Co-authored-by: Adam Greig <adam@adamgreig.com>
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.
This is a first go at running CI jobs on a scheduled basis. This job will run at 7pm UTC today (Wednesday), run our tests, and, in this case, fail. On failure it should then open a new issue on the repository with a link to the failed CI job.
We can bikeshed the schedule (this is just to get it to run soonish), and obviously I'll do another PR to remove the failing step once we've checked it works.
Please don't merge if we miss 7pm weds; I'll update the schedule first.