Wasmtime GitHub notifications bot (Feb 22 2022 at 18:52): Wasmtime GitHub notifications bot (Feb 22 2022 at 18:52):alexcrichton opened PR #3834 from triage-less to main:
Triage is scheduled to run once every 5 minutes but it's often queued up
during the day as builders are otherwise occupied with actual CI builds.
This can end up in a lot of triage tasks queued up back-to-back. While
this doesn't seem to be a huge issue one thing I suspect is that this is
perhaps somewhat related to API rate limits getting hit when recent
versions were published. In any case there's no need for each and every
triage run to do something, it's fine to only have one at a time
pending.<!--
Please ensure that the following steps are all taken care of before submitting
the PR.
[ ] This has been discussed in issue #..., or if not, please tell us why
here.[ ] A short description of what this does, why it is needed; if the
description becomes long, the matter should probably be discussed in an issue
first.[ ] This PR contains test cases, if meaningful.
- [ ] A reviewer from the core maintainer team has been assigned for this PR.
If you don't know who could review this, please indicate so. The list of
suggested reviewers on the right can help you.Please ensure all communication adheres to the code of conduct.
-->
Wasmtime GitHub notifications bot (Feb 22 2022 at 18:59):fitzgen submitted PR review.
Wasmtime GitHub notifications bot (Feb 22 2022 at 18:59):fitzgen submitted PR review.
Wasmtime GitHub notifications bot (Feb 22 2022 at 18:59):fitzgen created PR review comment:
It is sort of unfortunate that we have to cancel in-progress jobs rather than cancel ourselves since there is already a job in progress :-/
Wasmtime GitHub notifications bot (Feb 22 2022 at 19:24):alexcrichton merged PR #3834.
Last updated: Nov 22 2024 at 17:03 UTC