Problem running the latest python2-2.7.14-1 under AppVeyor

Problem running the latest python2-2.7.14-1 under AppVeyor

[Vadim Zeitlin]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1727 bytes --]

 Hello,

 Our build has started on AppVeyor, a continuous integration provider,
started failing since a couple of days as a makefile command running a
Python script started failing with exit code 127 without any more
information. This is a strange situation as I can't reproduce the problem
locally, but something definitely seems to be wrong with this package on
the AppVeyor machine as Python just doesn't seem to be executable, e.g. the
output of these commands in our batch file driving the build:

	echo --- Python version:
	python -V
	echo --- Python used by bash:
	bash -c "command -v python"
	echo --- Python version from bash:
	bash -c "python -V"
	echo --- Configuring:

is (see https://ci.appveyor.com/project/wxWidgets/wxwidgets/build/job/j8tundwivyvnghrf)

	--- Python version:
	Python 2.7.13
	--- Python used by bash:
	/usr/bin/python
	--- Python version from bash:
	--- Configuring:

I.e. both native and Cygwin Python versions are installed, but the latter
one doesn't seem to be executable.

 The same log also contains the following lines

Downloaded C:/cygwin/var/cache/setup/http%3a%2f%2fcygwin.mirror.constant.com%2f/x86/release/python2/python2-2.7.14-1.tar.xz
...
Extracting from file://C:/cygwin/var/cache/setup/http%3a%2f%2fcygwin.mirror.constant.com%2f/x86/release/python2/python2-2.7.14-1.tar.xz

a bit earlier, and as things worked fine with Cygwin 2.7.13 package before,
it seems that 2.7.14 broke something, but I have no idea what nor how to
fix it.

 We'll just work around using Python in our Cygwin build for now, so it's
not a critical problem for us, but I wanted to report it here, even if I
realize that this report is not very detailed, just in case it could be
useful.

 Best regards,
VZ

[-- Attachment #2: Type: APPLICATION/PGP-SIGNATURE, Size: 196 bytes --]

Re: Problem running the latest python2-2.7.14-1 under AppVeyor

[Erik Bray]

On Fri, Nov 3, 2017 at 3:45 PM, Vadim Zeitlin wrote:
>  Hello,
>
>  Our build has started on AppVeyor, a continuous integration provider,
> started failing since a couple of days as a makefile command running a
> Python script started failing with exit code 127 without any more
> information. This is a strange situation as I can't reproduce the problem
> locally, but something definitely seems to be wrong with this package on
> the AppVeyor machine as Python just doesn't seem to be executable, e.g. the
> output of these commands in our batch file driving the build:
>
>         echo --- Python version:
>         python -V
>         echo --- Python used by bash:
>         bash -c "command -v python"
>         echo --- Python version from bash:
>         bash -c "python -V"
>         echo --- Configuring:
>
> is (see https://ci.appveyor.com/project/wxWidgets/wxwidgets/build/job/j8tundwivyvnghrf)
>
>         --- Python version:
>         Python 2.7.13
>         --- Python used by bash:
>         /usr/bin/python
>         --- Python version from bash:
>         --- Configuring:
>
> I.e. both native and Cygwin Python versions are installed, but the latter
> one doesn't seem to be executable.
>
>  The same log also contains the following lines
>
> Downloaded C:/cygwin/var/cache/setup/http%3a%2f%2fcygwin.mirror.constant.com%2f/x86/release/python2/python2-2.7.14-1.tar.xz
> ...
> Extracting from file://C:/cygwin/var/cache/setup/http%3a%2f%2fcygwin.mirror.constant.com%2f/x86/release/python2/python2-2.7.14-1.tar.xz
>
> a bit earlier, and as things worked fine with Cygwin 2.7.13 package before,
> it seems that 2.7.14 broke something, but I have no idea what nor how to
> fix it.
>
>  We'll just work around using Python in our Cygwin build for now, so it's
> not a critical problem for us, but I wanted to report it here, even if I
> realize that this report is not very detailed, just in case it could be
> useful.

Hi,

I couldn't tell you exactly what the problem is (though I'd be curious
to find out, as I'm doing some builds with Cygwin on AppVeyor as well
so it might be relevant to me).

However, I noticed that you are installing your own Cygwin--were you
aware that (most, at least?) of AppVeyor's base images comes with
Cygwin pre-installed.  And this is more "stable" insofar as the Cygwin
version and all pre-installed packages are pinned, at least, until
AppVeyor updates the image (which I actually need to get them to do,
since the pre-installed Cygwin is currently at 2.8.0, and I would like
2.8.1...).

So my point is, have you tried using the pre-installed Cygwin?

Best,
Erik

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Problem running the latest python2-2.7.14-1 under AppVeyor

[Jon Turney]

On 03/11/2017 14:45, Vadim Zeitlin wrote:
> Our build has started on AppVeyor, a continuous integration provider,
> started failing since a couple of days as a makefile command running a
> Python script started failing with exit code 127 without any more
> information. This is a strange situation as I can't reproduce the problem
> locally, but something definitely seems to be wrong with this package on
> the AppVeyor machine as Python just doesn't seem to be executable, e.g. the
> output of these commands in our batch file driving the build:

Perhaps you need to provide the -g (--upgrade-also) flag to cygwin's setup.

Due to setup terribleness, without this flag, it will install the 
requested packages, and any missing dependencies of them, but not 
upgrade any of the dependencies which are already installed to the 
current (and perhaps needed) version...

See also [1].

[1] https://sourceware.org/ml/cygwin/2017-03/msg00365.html


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re[2]: Problem running the latest python2-2.7.14-1 under AppVeyor

[Vadim Zeitlin]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1145 bytes --]

On Fri, 3 Nov 2017 15:26:27 +0000 Jon Turney <jon.turney@dronecode.org.uk> wrote:

JT> On 03/11/2017 14:45, Vadim Zeitlin wrote:
JT> > Our build has started on AppVeyor, a continuous integration provider,
JT> > started failing since a couple of days as a makefile command running a
JT> > Python script started failing with exit code 127 without any more
JT> > information. This is a strange situation as I can't reproduce the problem
JT> > locally, but something definitely seems to be wrong with this package on
JT> > the AppVeyor machine as Python just doesn't seem to be executable, e.g. the
JT> > output of these commands in our batch file driving the build:
JT> 
JT> Perhaps you need to provide the -g (--upgrade-also) flag to cygwin's setup.

 Thank you! This has indeed fixed it and Python runs now, after having
updated a whole lot of other packages[*]. And it also explains why I failed
to reproduce it locally: it must have installed all the right versions of
the packages for me, as I hadn't had them before.

 Thanks again for helping with resolving this issue!
VZ

[*] https://ci.appveyor.com/project/wxWidgets/wxwidgets/build/2248

[-- Attachment #2: Type: APPLICATION/PGP-SIGNATURE, Size: 196 bytes --]