From: Stephen Kitt <steve@sk2.org>
To: Jan Beulich <jbeulich@suse.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH v2] tests: force non-deterministic mode in non-deterministic tests
Date: Thu, 21 Dec 2023 09:13:37 +0100 [thread overview]
Message-ID: <20231221091337.4800b743@heffalump.sk2.org> (raw)
In-Reply-To: <2db63c69-1b7f-4914-9bb0-a3fee24bc1cd@suse.com>
[-- Attachment #1: Type: text/plain, Size: 1210 bytes --]
On Thu, 21 Dec 2023 08:22:43 +0100, Jan Beulich <jbeulich@suse.com> wrote:
> On 20.12.2023 18:40, Stephen Kitt wrote:
> > Incidentally, builds with this patch in Debian all pass these tests (with
> > SOURCE_DATE_EPOCH set in the environment), but fail on i386 tests on
> > big-endian systems; see
> > https://buildd.debian.org/status/package.php?p=binutils-mingw-w64 for
> > logs. git bisect tells me that the culprit is
> > 734dfd1cc966aff736eaeda68bfa4807ee4b50c1 but I haven’t figured out why
> > yet.
>
> That has been there for a while. I would have looked at the build logs, but
> the link above points only at their tails, and I can't spot how to obtain
> them through just the browser (needing to obtain any debian specific
> software for this purpose is a no-go imo).
Of course! It’s not obvious, you can get the full logs by following the
“Build-Attempted” links. For example,
https://buildd.debian.org/status/fetch.php?pkg=binutils-mingw-w64&arch=s390x&ver=11.2&stamp=1703021196&raw=0
on s390x.
To reproduce this, on any BE system (s390x, sparc64 etc.), on current trunk:
./configure --target=i686-w64-mingw32 && make && make -C gas check
Regards,
Stephen
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-12-21 8:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 21:53 Stephen Kitt
2023-12-20 8:03 ` Jan Beulich
2023-12-20 17:40 ` Stephen Kitt
2023-12-21 7:22 ` Jan Beulich
2023-12-21 8:13 ` Stephen Kitt [this message]
2023-12-21 8:34 ` Jan Beulich
2023-12-22 11:29 ` Jan Beulich
2023-12-22 22:03 ` Stephen Kitt
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=20231221091337.4800b743@heffalump.sk2.org \
--to=steve@sk2.org \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.com \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).