how to fix appveyor red status?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

how to fix appveyor red status?

Nicolas Cellier
 
Hi all,
anybody has an idea of what happens in the appveyor builds?

The 64bit squeak.stack.spur started to fail with:

https://ci.appveyor.com/project/OpenSmalltalk/vm/build/1.0.547/job/28bqcbsldbraq9nx

x86_64-w64-mingw32-clang -o mkNamedPrims.exe -mconsole -m64 ../../platforms/win32/util/mkNamedPrims.c
make: *** [../common/Makefile:202: mkNamedPrims.exe] Error 127
Command exited with code 1

Then it did propagate to most of the 32bits builds (but 2)

It seems completely unrelated to the committed changes, and I can't reproduce in any of my virtual windows machines.

Is it a change in cygwin, or anything else in the appveyor infrastucture?
How can we debug that?

Nicolas
Reply | Threaded
Open this post in threaded view
|

Re: how to fix appveyor red status?

Nicolas Cellier
 
If I google "appveyor Errror 127" I got matches like
https://github.com/appveyor/ci/issues/1210

maybe a clue...

2017-03-05 10:48 GMT+01:00 Nicolas Cellier <[hidden email]>:
Hi all,
anybody has an idea of what happens in the appveyor builds?

The 64bit squeak.stack.spur started to fail with:

https://ci.appveyor.com/project/OpenSmalltalk/vm/build/1.0.547/job/28bqcbsldbraq9nx

x86_64-w64-mingw32-clang -o mkNamedPrims.exe -mconsole -m64 ../../platforms/win32/util/mkNamedPrims.c
make: *** [../common/Makefile:202: mkNamedPrims.exe] Error 127
Command exited with code 1

Then it did propagate to most of the 32bits builds (but 2)

It seems completely unrelated to the committed changes, and I can't reproduce in any of my virtual windows machines.

Is it a change in cygwin, or anything else in the appveyor infrastucture?
How can we debug that?

Nicolas

Reply | Threaded
Open this post in threaded view
|

Re: how to fix appveyor red status?

Holger Freyther
 

> On 5 Mar 2017, at 10:50, Nicolas Cellier <[hidden email]> wrote:
>
> If I google "appveyor Errror 127" I got matches like
> https://github.com/appveyor/ci/issues/1210
>

http://help.appveyor.com/discussions/problems/6165-mingw64-i686-gcc-g-540-4tarxz-somehow-broken

in the pharo build I avoided the issue by installing "5.4.0-3" (and then opening the discussion on appveyor). In the #cygwin irc channel other people don't seem to run into the issue.

holger
Reply | Threaded
Open this post in threaded view
|

Re: how to fix appveyor red status?

fniephaus
In reply to this post by Nicolas Cellier
 
I think I know what's going on and I'll try to fix it tomorrow. 
Error 127 means that it was unable to find a command (e.g. unzip).

Fabio

On Sun, 5 Mar 2017 at 10:50, Nicolas Cellier <[hidden email]> wrote:
 
If I google "appveyor Errror 127" I got matches like
https://github.com/appveyor/ci/issues/1210

maybe a clue...

2017-03-05 10:48 GMT+01:00 Nicolas Cellier <[hidden email]>:
Hi all,
anybody has an idea of what happens in the appveyor builds?

The 64bit squeak.stack.spur started to fail with:

https://ci.appveyor.com/project/OpenSmalltalk/vm/build/1.0.547/job/28bqcbsldbraq9nx

x86_64-w64-mingw32-clang -o mkNamedPrims.exe -mconsole -m64 ../../platforms/win32/util/mkNamedPrims.c
make: *** [../common/Makefile:202: mkNamedPrims.exe] Error 127
Command exited with code 1

Then it did propagate to most of the 32bits builds (but 2)

It seems completely unrelated to the committed changes, and I can't reproduce in any of my virtual windows machines.

Is it a change in cygwin, or anything else in the appveyor infrastucture?
How can we debug that?

Nicolas

Reply | Threaded
Open this post in threaded view
|

Re: how to fix appveyor red status?

Nicolas Cellier
 
Thanks Holger and Fabio,
I think I now found a better match ;)

https://github.com/appveyor/ci/issues/1356

2017-03-05 13:14 GMT+01:00 Fabio Niephaus <[hidden email]>:
 
I think I know what's going on and I'll try to fix it tomorrow. 
Error 127 means that it was unable to find a command (e.g. unzip).

Fabio

On Sun, 5 Mar 2017 at 10:50, Nicolas Cellier <[hidden email]> wrote:
 
If I google "appveyor Errror 127" I got matches like
https://github.com/appveyor/ci/issues/1210

maybe a clue...

2017-03-05 10:48 GMT+01:00 Nicolas Cellier <[hidden email]>:
Hi all,
anybody has an idea of what happens in the appveyor builds?

The 64bit squeak.stack.spur started to fail with:

https://ci.appveyor.com/project/OpenSmalltalk/vm/build/1.0.547/job/28bqcbsldbraq9nx

x86_64-w64-mingw32-clang -o mkNamedPrims.exe -mconsole -m64 ../../platforms/win32/util/mkNamedPrims.c
make: *** [../common/Makefile:202: mkNamedPrims.exe] Error 127
Command exited with code 1

Then it did propagate to most of the 32bits builds (but 2)

It seems completely unrelated to the committed changes, and I can't reproduce in any of my virtual windows machines.

Is it a change in cygwin, or anything else in the appveyor infrastucture?
How can we debug that?

Nicolas



Reply | Threaded
Open this post in threaded view
|

Re: how to fix appveyor red status?

fniephaus
 

On Sun, 5 Mar 2017 at 13:59, Nicolas Cellier <[hidden email]> wrote:
 
Thanks Holger and Fabio,
I think I now found a better match ;)

https://github.com/appveyor/ci/issues/1356


2017-03-05 13:14 GMT+01:00 Fabio Niephaus <[hidden email]>:
 
I think I know what's going on and I'll try to fix it tomorrow. 
Error 127 means that it was unable to find a command (e.g. unzip).

Fabio

On Sun, 5 Mar 2017 at 10:50, Nicolas Cellier <[hidden email]> wrote:
 
If I google "appveyor Errror 127" I got matches like
https://github.com/appveyor/ci/issues/1210

maybe a clue...

2017-03-05 10:48 GMT+01:00 Nicolas Cellier <[hidden email]>:
Hi all,
anybody has an idea of what happens in the appveyor builds?

The 64bit squeak.stack.spur started to fail with:

https://ci.appveyor.com/project/OpenSmalltalk/vm/build/1.0.547/job/28bqcbsldbraq9nx

x86_64-w64-mingw32-clang -o mkNamedPrims.exe -mconsole -m64 ../../platforms/win32/util/mkNamedPrims.c
make: *** [../common/Makefile:202: mkNamedPrims.exe] Error 127
Command exited with code 1

Then it did propagate to most of the 32bits builds (but 2)

It seems completely unrelated to the committed changes, and I can't reproduce in any of my virtual windows machines.

Is it a change in cygwin, or anything else in the appveyor infrastucture?
How can we debug that?

Nicolas



Reply | Threaded
Open this post in threaded view
|

Re: how to fix appveyor red status?

Nicolas Cellier
 
Thanks again, super effective!

2017-03-05 16:17 GMT+01:00 Fabio Niephaus <[hidden email]>:
 

On Sun, 5 Mar 2017 at 13:59, Nicolas Cellier <[hidden email]> wrote:
 
Thanks Holger and Fabio,
I think I now found a better match ;)

https://github.com/appveyor/ci/issues/1356


2017-03-05 13:14 GMT+01:00 Fabio Niephaus <[hidden email]>:
 
I think I know what's going on and I'll try to fix it tomorrow. 
Error 127 means that it was unable to find a command (e.g. unzip).

Fabio

On Sun, 5 Mar 2017 at 10:50, Nicolas Cellier <[hidden email]> wrote:
 
If I google "appveyor Errror 127" I got matches like
https://github.com/appveyor/ci/issues/1210

maybe a clue...

2017-03-05 10:48 GMT+01:00 Nicolas Cellier <[hidden email]>:
Hi all,
anybody has an idea of what happens in the appveyor builds?

The 64bit squeak.stack.spur started to fail with:

https://ci.appveyor.com/project/OpenSmalltalk/vm/build/1.0.547/job/28bqcbsldbraq9nx

x86_64-w64-mingw32-clang -o mkNamedPrims.exe -mconsole -m64 ../../platforms/win32/util/mkNamedPrims.c
make: *** [../common/Makefile:202: mkNamedPrims.exe] Error 127
Command exited with code 1

Then it did propagate to most of the 32bits builds (but 2)

It seems completely unrelated to the committed changes, and I can't reproduce in any of my virtual windows machines.

Is it a change in cygwin, or anything else in the appveyor infrastucture?
How can we debug that?

Nicolas