Our pythontestdotnet repo is different than the cpython repo and the certificate gets pushed to the server after being committed by hand so it's a synchronization problem,.

https://github.com/python/cpython/pull/13192 should clear it up.  It's awaiting the slow CI queuing gods.  It is marked automerge, so if a core dev could go do a github review and Approve it, it'll go in immediately after Travis and AppVeyor come back green. 


On Wed, May 8, 2019 at 10:58 AM Antoine Pitrou <antoine@python.org> wrote:

Ok, apparently the SSL cert on self-signed.pythontest.net was changed
but it wasn't updated in our source tree, hence the failure.



Le 08/05/2019 à 17:49, Mariatta a écrit :
> If you can't merge from GitHub UI then you won't be able to do it from
> GitHub command line (it respects the same branch protection policy)
> I don't think we should merge if tests are still failing. Perhaps the
> test should be adjusted to handle this spurious errors? Can it be marked
> as "allowed failure" or something like that?
> On Wed, May 8, 2019, 8:32 AM Antoine Pitrou <antoine@python.org
> <mailto:antoine@python.org>> wrote:
>     Hello,
>     There are spurious CI failures (SSL certificate issue in test_httplib).
>     Therefore the "Squash and merge" button is greyed out.
>     How should I merge? Using the command-line instructions from Github?
>     Regards
>     Antoine.
>     _______________________________________________
>     python-committers mailing list
>     python-committers@python.org <mailto:python-committers@python.org>
>     https://mail.python.org/mailman/listinfo/python-committers
>     Code of Conduct: https://www.python.org/psf/codeofconduct/
python-committers mailing list
Code of Conduct: https://www.python.org/psf/codeofconduct/