[Python-Dev] Slipping Python 3.5.5rc1 and 3.4.8rc1 because of a Travis CI issue--can someone make Travis CI happy? (original) (raw)

Brett Cannon brett at python.org
Mon Jan 22 10:51:37 EST 2018

I can switch off the requirement that holds admins to having to pass the same status checks as everyone else (there's still a big warning when you exercise this power), that way you can override the merge if you want. Not sure if you want to ignore the CI in that case as well.

On Mon, 22 Jan 2018 at 02:33 Larry Hastings <larry at hastings.org> wrote:

I have three PRs for Python 3.5.5rc1: https://github.com/python/cpython/pull/4656 https://github.com/python/cpython/pull/5197 https://github.com/python/cpython/pull/5201 I can't merge them because Travis CI is unhappy. All three CI tests fail in the same way, reporting this error: The command "pyenv global system 3.5" failed and exited with 1 during . Since Travis CI is a "required check", Github won't let me merge the PR. Yes I could manually merge the patches by hand but I'm hoping it doesn't come to that. I'm slipping 3.4.8rc1 because I prefer to do both releases at once. I'm hoping this problem will be resolved quickly; if we only slip the RCs by a day or two I won't slip the final releases (in about two weeks). PLS SND HALP, /arry

Python-Dev mailing list Python-Dev at python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/brett%40python.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20180122/666b1902/attachment.html>

More information about the Python-Dev mailing list