Re: [Python-Dev] Slipping Python 3.5.5rc1 and 3.4.8rc1 because of a Travis CI issue--can someone make Travis CI happy?

2018-01-22 Thread Nick Coghlan 
On 22 January 2018 at 20:57, Victor Stinner  wrote:
> I created an issue with more information:
> https://bugs.python.org/issue32620

We shouldn't be requiring a pre-existing Python to build CPython
anyway, so it would be nice if we could just delete that step
entirely.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncogh...@gmail.com   |   Brisbane, Australia
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Slipping Python 3.5.5rc1 and 3.4.8rc1 because of a Travis CI issue--can someone make Travis CI happy?

2018-01-22 Thread Larry Hastings 



On 01/22/2018 07:51 AM, Brett Cannon wrote:
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.


Yes, please.  I'll make you a deal: I'll download and apply the patches 
manually and run the test suite.  I'll only merge if the patch doesn't 
cause test failures.


It'd be swell if we could actually fix the builds on Travis CI 
naturally.  I assume that will happen eventually, but I don't want to 
hold up the rc's for that.


Thanks,


//arry/
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Slipping Python 3.5.5rc1 and 3.4.8rc1 because of a Travis CI issue--can someone make Travis CI happy?

2018-01-22 Thread Brett Cannon 
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  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@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/brett%40python.org
>
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Slipping Python 3.5.5rc1 and 3.4.8rc1 because of a Travis CI issue--can someone make Travis CI happy?

2018-01-22 Thread Stéfane Fermigier 
On Mon, Jan 22, 2018 at 11:33 AM, Larry Hastings  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 .
>
>
This seems to be related to
https://github.com/travis-ci/travis-ci/issues/8363

  S.

-- 
Stefane Fermigier - http://fermigier.com/ - http://twitter.com/sfermigier -
http://linkedin.com/in/sfermigier
Founder & CEO, Abilian - Enterprise Social Software -
http://www.abilian.com/
Chairman, Free Group / Systematic Cluster -
http://www.gt-logiciel-libre.org/
Co-Chairman, National Council for Free & Open Source Software (CNLL) -
http://cnll.fr/
Founder & Organiser, PyData Paris - http://pydata.fr/
---
“You never change things by fighting the existing reality. To change
something, build a new model that makes the existing model obsolete.” — R.
Buckminster Fuller
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Slipping Python 3.5.5rc1 and 3.4.8rc1 because of a Travis CI issue--can someone make Travis CI happy?

2018-01-22 Thread Joni Orponen 
On Mon, Jan 22, 2018 at 11:59 AM, Oleg Broytman  wrote:

> On Mon, Jan 22, 2018 at 02:33:01AM -0800, Larry Hastings <
> la...@hastings.org> wrote:
> > All ... CI tests fail in
> > the same way, reporting this error:
> >
> >The command "pyenv global system 3.5" failed and exited with 1 during
> .
>
>Seems there is a slow workaround (install python 3.5):
>
> https://github.com/travis-ci/travis-ci/issues/8363#issuecomment-354857845
>
> which python3.5 || (pyenv install 3.5.4 && pyenv use system 3.5.4)
>

There is also https://github.com/praekeltfoundation/travis-pyenv I've found
useful when one needs excactness and also to decouple oneself from the
Travis side rolling releases of Python. Also caches the Python version for
you.

See
https://github.com/plone/plone.intelligenttext/blob/a71bdc5b485b1562b2e320f5c41a15286f205f98/.travis.yml
for a usage example.

-- 
Joni Orponen
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Slipping Python 3.5.5rc1 and 3.4.8rc1 because of a Travis CI issue--can someone make Travis CI happy?

2018-01-22 Thread Oleg Broytman 
On Mon, Jan 22, 2018 at 02:33:01AM -0800, Larry Hastings  
wrote:
> All ... CI tests fail in
> the same way, reporting this error:
> 
>The command "pyenv global system 3.5" failed and exited with 1 during .

   Seems there is a slow workaround (install python 3.5):

https://github.com/travis-ci/travis-ci/issues/8363#issuecomment-354857845

which python3.5 || (pyenv install 3.5.4 && pyenv use system 3.5.4)

> //arry/

Oleg.
-- 
 Oleg Broytmanhttp://phdru.name/p...@phdru.name
   Programmers don't die, they just GOSUB without RETURN.
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Slipping Python 3.5.5rc1 and 3.4.8rc1 because of a Travis CI issue--can someone make Travis CI happy?

2018-01-22 Thread Victor Stinner 
I created an issue with more information:
https://bugs.python.org/issue32620

Victor

2018-01-22 11:33 GMT+01:00 Larry Hastings :
>
>
> 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@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/victor.stinner%40gmail.com
>
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

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

2018-01-22 Thread Larry Hastings 



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@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com