Mariatta mariatta at python.org
Wed May 8 11:49:47 EDT 2019

• Previous message (by thread): [python-committers] Merge with spurious CI failures?
• Next message (by thread): [python-committers] Merge with spurious CI failures?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

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 at 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 at python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20190508/cf6195b4/attachment.html>

---

• Previous message (by thread): [python-committers] Merge with spurious CI failures?
• Next message (by thread): [python-committers] Merge with spurious CI failures?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the python-committers mailing list