rust-lang / rust-lang/rust-playground
Nightly cron update runs considerably after the new nightly has been released
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.4k
- Forks
- 268
- Avg merge
- 3h 2m
- Merged PRs (30d)
- 6
Description
It looks like the nightly update on the playground runs around 8am UTC, i.e., quite considerably after the new nightly has been released. It just happened the second time that I went to the playground in the morning to play with a feature that landed the day before and was surprised why it was not available yet. ;)
Unfortunately, Travis cron job configuration is quite awful and does not let you pick the time the job runs. So to move it earlier, you have to be awake at that time and then delete and re-configure the cron job in the travis settings. However, if you are in the US timezone, that means it shouldn't be too hard to get one configured for around 3am UTC (9am at the East Coast) or so, when the new nightly should definitely be up. Being in a European timezone, my own cron jobs usually run around 7am UTC as I rarely get up earlier than that...^^
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Travis CI playground job and the repository's Travis cron configuration. Compare the job's run time with the nightly release time, then update the Travis cron schedule to run around 3am UTC and confirm a subsequent run picks up the new nightly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100