Re: Please give back golang-1.8 (1.8.3-1) on s390x

[Julien Cristau]

On Sun, Jun 25, 2017 at 08:42:17 -0600, Anthony Fok wrote:

> On Sat, Jun 24, 2017 at 2:58 PM, Aurelien Jarno  wrote:
> > On 2017-06-24 11:15, Anthony Fok wrote:
> >> Or, better yet, is there a way to find out what went wrong on
> >> zemlinsky?  Is it an older machine with an older CPU that does not
> >> support some newer CPU instructions?  (Sorry, I know nothing about
> >> s390x and I am likely completely wrong.)
> >
> > That is actually the problem. On s390x golang requires a higher ISA than
> > the one Debian targets. I have started to patch golang-1.7 to avoid these
> > new instructions a few months ago, but upstream is not interested by
> > supporting older CPUs and keep adding more usage of new instructions.
> 
> Thank you for your detailed explanation, and thank you for your
> efforts in trying to solve it.
> 
> But yeah, I guess golang users on s390x would just have to accept the
> fact that they need a newer CPU.  Thankfully, the majority of Debian's
> s390x machines (buildd and porterbox), 3 out of 4, support the newer
> instructions.  :-)
> 
I don't think that's acceptable.  We should not ship packages that won't
work on the baseline platform for each architecture.  We should either
fix those packages, stop shipping them, or raise the baseline.

Cheers,
Julien

Re: Please give back golang-1.8 (1.8.3-1) on s390x

[Philipp Kern]

On 06/25/2017 04:42 PM, Anthony Fok wrote:
>>> Or, better yet, is there a way to find out what went wrong on
>>> zemlinsky?  Is it an older machine with an older CPU that does not
>>> support some newer CPU instructions?  (Sorry, I know nothing about
>>> s390x and I am likely completely wrong.)
>>
>> That is actually the problem. On s390x golang requires a higher ISA than
>> the one Debian targets. I have started to patch golang-1.7 to avoid these
>> new instructions a few months ago, but upstream is not interested by
>> supporting older CPUs and keep adding more usage of new instructions.
> 
> Thank you for your detailed explanation, and thank you for your
> efforts in trying to solve it.
> 
> But yeah, I guess golang users on s390x would just have to accept the
> fact that they need a newer CPU.  Thankfully, the majority of Debian's
> s390x machines (buildd and porterbox), 3 out of 4, support the newer
> instructions.  :-)

What's the current ISA requirement for golang? zEC12? z13?

I suppose popcon (as misleading as it is) likely doesn't have h/w stats?
(And I know that the current count of actual submissions is... 12.)

Kind regards and thanks
Philipp Kern

Re: Please give back golang-1.8 (1.8.3-1) on s390x

[Anthony Fok]

On Sat, Jun 24, 2017 at 2:58 PM, Aurelien Jarno  wrote:
> On 2017-06-24 11:15, Anthony Fok wrote:
>> There seems to be a hiccup when golang-1.8 (1.8.3-1) was last built
>> for s390x on zemlinsky.
>>
>> Seeing the logs at
>>
>> https://buildd.debian.org/status/logs.php?pkg=golang-1.8=s390x
>>
>> It seems that zemlinsky fails consistently "Illegal Instruction" early
>> in the build,
>> while both zandonai and zani consistently succeed.
>>
>> gb golang-1.8_1.8.3-1 . s390x
>
> Done.

Thank you so much, Aurelien!

>> Perhaps it is too much to ask, but would it be possible to set some
>> kind of automatic give-back whenever golang-1.8 (or future golang-1.9)
>> fails on zemlinsky?
>
> Automatic give back no, but we can blacklist the package on this build
> daemon. This is only a workaround for the problem below.

Even better!  Thank you!

>> Or, better yet, is there a way to find out what went wrong on
>> zemlinsky?  Is it an older machine with an older CPU that does not
>> support some newer CPU instructions?  (Sorry, I know nothing about
>> s390x and I am likely completely wrong.)
>
> That is actually the problem. On s390x golang requires a higher ISA than
> the one Debian targets. I have started to patch golang-1.7 to avoid these
> new instructions a few months ago, but upstream is not interested by
> supporting older CPUs and keep adding more usage of new instructions.

Thank you for your detailed explanation, and thank you for your
efforts in trying to solve it.

But yeah, I guess golang users on s390x would just have to accept the
fact that they need a newer CPU.  Thankfully, the majority of Debian's
s390x machines (buildd and porterbox), 3 out of 4, support the newer
instructions.  :-)

Cheers,
Anthony

Re: Please give back golang-1.8 (1.8.3-1) on s390x

[Aurelien Jarno]

On 2017-06-24 11:15, Anthony Fok wrote:
> Hello,
> 
> There seems to be a hiccup when golang-1.8 (1.8.3-1) was last built
> for s390x on zemlinsky.
> 
> Seeing the logs at
> 
> https://buildd.debian.org/status/logs.php?pkg=golang-1.8=s390x
> 
> It seems that zemlinsky fails consistently "Illegal Instruction" early
> in the build,
> while both zandonai and zani consistently succeed.
> 
> gb golang-1.8_1.8.3-1 . s390x

Done.

> Perhaps it is too much to ask, but would it be possible to set some
> kind of automatic give-back whenever golang-1.8 (or future golang-1.9)
> fails on zemlinsky?

Automatic give back no, but we can blacklist the package on this build
daemon. This is only a workaround for the problem below.

> Or, better yet, is there a way to find out what went wrong on
> zemlinsky?  Is it an older machine with an older CPU that does not
> support some newer CPU instructions?  (Sorry, I know nothing about
> s390x and I am likely completely wrong.)

That is actually the problem. On s390x golang requires a higher ISA than
the one Debian targets. I have started to patch golang-1.7 to avoid these
new instructions a few months ago, but upstream is not interested by
supporting older CPUs and keep adding more usage of new instructions.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Please give back golang-1.8 (1.8.3-1) on s390x

[Anthony Fok]

Hello,

There seems to be a hiccup when golang-1.8 (1.8.3-1) was last built
for s390x on zemlinsky.

Seeing the logs at

https://buildd.debian.org/status/logs.php?pkg=golang-1.8=s390x

It seems that zemlinsky fails consistently "Illegal Instruction" early
in the build,
while both zandonai and zani consistently succeed.

gb golang-1.8_1.8.3-1 . s390x

Perhaps it is too much to ask, but would it be possible to set some
kind of automatic give-back whenever golang-1.8 (or future golang-1.9)
fails on zemlinsky?

Or, better yet, is there a way to find out what went wrong on
zemlinsky?  Is it an older machine with an older CPU that does not
support some newer CPU instructions?  (Sorry, I know nothing about
s390x and I am likely completely wrong.)

Many thanks!

Anthony