From: Axel Beckert <abe@deuxchevaux.org>
To: zsh-workers@zsh.org
Subject: Re: 5.0.5-dev-3
Date: Thu, 28 Aug 2014 21:54:49 +0200 [thread overview]
Message-ID: <20140828195449.GU7356@sym.noone.org> (raw)
In-Reply-To: <20140827162834.GQ7356@sym.noone.org>
Hi,
JFYI:
On Wed, Aug 27, 2014 at 06:28:34PM +0200, Axel Beckert wrote:
> We again got a few build-failures on the build daemons, but this time
> on different architectures than with 5.0.5-dev-2, namely amd64 (Linux)
> and s390x while kfreebsd-amd64 worked fine this time:
>
> https://buildd.debian.org/status/package.php?p=zsh&suite=experimental
>
> On amd64 (aka x86_64) the testsuite was hanging and killed after 150
> minutes:
> https://buildd.debian.org/status/fetch.php?pkg=zsh&arch=amd64&ver=5.0.5-dev-3-1&stamp=1409099297
A second build (by just putting the package back into the build queue)
succeeded in this case.
So these test suite hangs are very likely non-deterministic. At least
not related to the build process in general. The two builds were on
different build daemon machines though. But in the meanwhile I doubt
that this makes a difference in this case as I had the issue once
locally and just the next built succeeded again.
> On s390x, gcc was killed after 150 minutes of inactivity:
> https://buildd.debian.org/status/fetch.php?pkg=zsh&arch=s390x&ver=5.0.5-dev-3-1&stamp=1409118602
>
> At the moment the latter looks more like a platform issue to me as the
> same happened with a rebuild of 5.0.5 due to glibc bugfixes while it
> didn't fail two months ago with a previous glibc version. I'll talk to
> the s390 porters about this.
Has been confirmed and a currently running second build is also bound
to fail: gcc seems subtly broken in Debian Unstable on s390x currently
for all packages which use sigjmp_buf directly or in a build
dependency.
Not our job. ;-)
Kind regards, Axel
--
/~\ Plain Text Ribbon Campaign | Axel Beckert
\ / Say No to HTML in E-Mail and News | abe@deuxchevaux.org (Mail)
X See http://www.nonhtmlmail.org/campaign.html | abe@noone.org (Mail+Jabber)
/ \ I love long mails: http://email.is-not-s.ms/ | http://noone.org/abe/ (Web)
next prev parent reply other threads:[~2014-08-28 19:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-24 17:39 5.0.5-dev-3 Peter Stephenson
2014-08-26 17:11 ` 5.0.5-dev-3 Dominic Hopf
2014-08-27 16:28 ` 5.0.5-dev-3 Axel Beckert
2014-08-28 19:54 ` Axel Beckert [this message]
2014-08-30 23:46 ` 5.0.5-dev-3 Axel Beckert
2014-08-30 23:25 ` "5 seconds to fail" 5.0.5-dev-3 Bart Schaefer
2014-09-29 1:20 ` "5 seconds to fail" Axel Beckert
2014-09-29 1:51 ` [Pkg-zsh-devel] Bug#760061: " Axel Beckert
2014-09-29 6:25 ` Bart Schaefer
2014-09-29 9:02 ` [Pkg-zsh-devel] Bug#760061: " Axel Beckert
2014-09-30 17:40 ` [Pkg-zsh-devel] " Axel Beckert
2014-10-01 7:12 ` Bart Schaefer
2014-10-01 8:51 ` Axel Beckert
2014-10-02 7:10 ` Axel Beckert
2014-10-02 15:30 ` Bart Schaefer
2014-10-02 15:57 ` Axel Beckert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140828195449.GU7356@sym.noone.org \
--to=abe@deuxchevaux.org \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).