> Is there a possible middle ground here? Rather than a required PR check
(or a full buildbot run), maybe we could just add a new “magic” label that
runs a single refleak job using the GitHub actions runners.
That sounds like a good compromise and it will be strictly better than the
current setup.
Is there a possible middle ground here? Rather than a required PR check (or a
full buildbot run), maybe we could just add a new “magic” label that runs a
single refleak job using the GitHub actions runners.
___
python-committers mailing list -- python-c
>
> > It is nigh impossible to pick out errors in a PR from flaky tests,
> flaky machines and pre-existing errors.
I agree with the sentiment but is certainly not that dramatic. We (people
watching the build bots) do it on a regular basis, and many contributors do
it very efficiently as well. I a
