Hi,
If someone sees a random issue on a CI, I suggest to open an issue at
bugs.python.org to track it. Otherwise, slowly, the number of random
failures becomes so high that it takes several "re-run all jobs"
steps, and so merging a basic typo fix takes 1 hour if not longer.
Victor
On Tue, Jun 22
Well, the 19 hours was just that I came back to the PR after 19 hours and
it was still not finished. I suspect that some message was just lost, and
either it never ran or was never marked as complete. :-)
On Tue, Jun 22, 2021 at 12:56 PM Alex Gaynor wrote:
> Yes, but at least you don't have to w
Yes, but at least you don't have to wait 19 hours to do so (github
actions also doesn't let you restart jobs until they're all completed,
or cancelled I suppose).
Alex
On Tue, Jun 22, 2021 at 3:54 PM Guido van Rossum wrote:
>
> That's too bad, we really should ask for this.
>
> A timeout on a jo
That's too bad, we really should ask for this.
A timeout on a job still marks it as failed, I presume, so we still have to
restart all jobs... :-(
On Tue, Jun 22, 2021 at 12:40 PM Alex Gaynor wrote:
> Github actions doesn't have the ability to restart individual jobs,
> sadly (I've asked for th
Github actions doesn't have the ability to restart individual jobs,
sadly (I've asked for this when they've done research sessions).
FWIW, I'd recommend adding a timeout to jobs (it can be set in the YML
file), that way hung jobs don't hang for hours and hours.
Alex
On Tue, Jun 22, 2021 at 3:16
