From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: 68229@debbugs.gnu.org
Cc: Efraim Flashner <efraim@flashner.co.il>
Subject: bug#68229: go.powerpc64le-linux 1.14.15 fails test suite
Date: Wed, 03 Jan 2024 11:29:50 -0500 [thread overview]
Message-ID: <87frze7535.fsf@gmail.com> (raw)
In-Reply-To: <3393@guix-ci.nnrss> (cuirass@gnu.org's message of "Wed, 03 Jan 2024 14:06:51 +0000")
Hello,
cuirass@gnu.org (Cuirass) writes:
> <p>The build <b>go.powerpc64le-linux</b> for specification <b>master</b> is broken. You can find the detailed information about this build <a
> href="https://ci.guix.gnu.org/build/3139760/details">here</a>.</p>
>
> https://ci.guix.gnu.org/build/3139760/details
The test failure is:
--8<---------------cut here---------------start------------->8---
--- FAIL: TestScript (0.00s)
--- FAIL: TestScript/vendor_complex (2.07s)
script_test.go:193:
# smoke test for complex build configuration (1.990s)
> go build -o complex.exe complex
> [exec:gccgo] go build -compiler=gccgo -o complex.exe complex
[stderr]
# complex
gccgo: error: unrecognized command-line option '-rpath=/gnu/store/qj6cnccz6vsffqa32rviw4zaqgh7xd6q-gcc-11.3.0-lib/lib'
[exit status 2]
FAIL: testdata/script/vendor_complex.txt:5: unexpected command failure
FAIL
FAIL cmd/go 46.068s
--8<---------------cut here---------------end--------------->8---
I don't see an obvious relationship with the recent commit touching
gccgo-12, but I'm CC'ing its author in case it could be.
--
Thanks,
Maxim
next parent reply other threads:[~2024-01-03 16:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3393@guix-ci.nnrss>
2024-01-03 16:29 ` Maxim Cournoyer [this message]
2024-01-03 16:53 ` bug#68229: go.powerpc64le-linux 1.14.15 fails test suite Efraim Flashner
2024-01-03 17:59 ` Maxim Cournoyer
[not found] ` <EC18D8A8-75C1-49D1-833B-B62F8D955E29@flashner.co.il>
2024-01-10 4:31 ` Maxim Cournoyer
2024-01-10 5:30 ` Efraim Flashner
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87frze7535.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=68229@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
/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.savannah.gnu.org/cgit/guix.git
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).