[python-committers] macOS Travis CI job became mandatory? (original) (raw)
Brett Cannon brett at python.org
Mon Jun 26 15:49:22 EDT 2017
- Previous message (by thread): [python-committers] macOS Travis CI job became mandatory?
- Next message (by thread): [python-committers] macOS Travis CI job became mandatory?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, 26 Jun 2017 at 09:22 Victor Stinner <victor.stinner at gmail.com> wrote:
2017-06-26 17:25 GMT+02:00 Antoine Pitrou <antoine at python.org>: > Given that it doesn't hurt to keep it, I would rather keep it. It > allows to quickly test for OS X-specific issues.
According to my bad experience of today, it took longer than 1h30 to get the [Merge] button... Before, it took around 20 min. Well, it only happed me once. Maybe macOS doesn't like Monday?
Anything in the Allowed Failures section, which is the macOS build and coverage, are totally optional and will not block you from merging. While they may keep the button from being green just to let you know some other things are still running, they won't block you from merging completely (that only happens if the docs or the main test run fail). -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-committers/attachments/20170626/adbe5f77/attachment.html>
- Previous message (by thread): [python-committers] macOS Travis CI job became mandatory?
- Next message (by thread): [python-committers] macOS Travis CI job became mandatory?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]