On 10Sep2019 0949, Benjamin Peterson wrote:
On Tue, Sep 10, 2019, at 08:54, Victor Stinner wrote:
Le lun. 9 sept. 2019 à 18:46, Benjamin Peterson <benja...@python.org> a écrit :
No one could think of a reason not to replace AppVeyor with Azure, so I've gone
ahead and done that on all those branches.
Here is a reason to not replace AppVEyor with Azure:
https://bugs.python.org/issue37245
The macOS job of Azure fails randomly, I reported the bug in June, no
one managed to fix it yet (Steve just made progress on it, thanks!),
and the whole Azure job is marked as "failed" if macOS fails. It seems
like it's yet another multiprocessing bug.
Would it be possible to change the macOS job of Azure to mark it as optional?
Someone familiar with pipelines would have to answer that.
I'm making a few updates to the Pipelines definition (which started as
enabling coverage, and then disabling it because it's *soooo* slow and
nobody seems to think we're using it on PRs anyway).
I believe I can make it so that the macOS test run times out after 20
minutes (~7 minutes longer than normal) and also that it's non-fatal,
without making the build on that platform non-fatal. But I'm pretty
convinced that the underlying issue here is a crash and we should
diagnose it.
My work is at https://github.com/python/cpython/pull/15827 for anyone
who'd like to follow along.
(Also, we don't have Pipelines configured for the 2.7 branch, so we
should keep AppVeyor on there.)
Cheers,
Steve
_______________________________________________
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/GUPCPLRDPTPCBJ2N2RYZSR4DTC5KPQBK/
Code of Conduct: https://www.python.org/psf/codeofconduct/
