> 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. In addition, I still think that for the slower tests, the git diff based test run can be quite beneficial. We just need to bear in mind that those tests will always be partial, so we should not be surprised if refleaks are still detected in buildbots. On Fri, 28 Jan 2022 at 14:25, Brandt Bucher <brandtbuc...@gmail.com> wrote: > 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-committers@python.org > To unsubscribe send an email to python-committers-le...@python.org > https://mail.python.org/mailman3/lists/python-committers.python.org/ > Message archived at > https://mail.python.org/archives/list/python-committers@python.org/message/NZ4N276GWJVCPU2VL2EDFTYUXWU4WCHR/ > Code of Conduct: https://www.python.org/psf/codeofconduct/ >
_______________________________________________ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-le...@python.org https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/python-committers@python.org/message/6LQSZLJ5QTB6732TDMCNEACTY6FKNUIP/ Code of Conduct: https://www.python.org/psf/codeofconduct/
