From: "Ludovic Courtès" <ludo@gnu.org>
To: bug-Guix@gnu.org
Subject: bug#37425: Go 1.12.7 fails to build on i686-linux
Date: Mon, 16 Sep 2019 14:41:59 +0200 [thread overview]
Message-ID: <87ef0gbeg8.fsf@gnu.org> (raw)
Hello,
Go 1.12.7 has test failures on i686-linux, on ‘core-updates’:
--8<---------------cut here---------------start------------->8---
ok path/filepath 0.041s
ok plugin 0.038s
ok reflect 0.328s
ok regexp 0.241s
ok regexp/syntax 1.026s
--- FAIL: TestGcSys (0.08s)
gc_test.go:33: expected "OK\n", but got "using too much memory: 17899520 bytes\n"
FAIL
FAIL runtime 37.967s
ok runtime/debug 0.103s
[…]
ok cmd/vendor/golang.org/x/sys/unix 0.391s
ok cmd/vet 8.529s
2019/09/16 12:33:32 Failed: exit status 1
command "sh" "all.bash" failed with status 1
builder for `/gnu/store/i2rs47n4000q9dh76alxvjgiry9pq6vj-go-1.12.7.drv' failed with exit code 1
--8<---------------cut here---------------end--------------->8---
(From
<https://ci.guix.gnu.org/log/pv1clywg43pb8fknrd2zs1zk4wd26fq0-go-1.12.7>.)
I found these issues that suggest the test has been flaky:
https://github.com/golang/go/issues/4155
https://github.com/golang/go/issues/28574
Unless someone has a better idea, I’d suggest skipping this test on
i686.
Thoughts?
Ludo’.
next reply other threads:[~2019-09-16 12:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 12:41 Ludovic Courtès [this message]
2019-09-16 21:59 ` bug#37425: Go 1.12.7 fails to build on i686-linux Ludovic Courtès
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=87ef0gbeg8.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bug-Guix@gnu.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.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).