From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] go1.13.1 build fails
Date: Sun, 6 Oct 2019 12:09:06 +0100 [thread overview]
Message-ID: <2eb38428179796cbf729751c27edbdb9@hamnavoe.com> (raw)
In-Reply-To: <CAJSxfmL2QZcjZyN34SFLbvb2zPQ8DeZH+p-XR3OASLzjGKm1_w@mail.gmail.com>
> go1.12.10 builds successfully but go1.13.1 fails. is it a known issue?
What platform? The build system is testing plan9/386, plan9/arm and plan9/amd64
on every commit so build failures shouldn't be slipping through. I've just
tested that release specifically on plan9/386 and it seems ok:
...
##### API check
Go version is "go1.13.1", ignoring -next /usr/miller/go1.13/api/next.txt
ALL TESTS PASSED
You might need to set GO_TEST_TIMEOUT_SCALE higher to avoid timeouts (it
defaults to 2 on arm, 4 on mips, 1 otherwise).
next prev parent reply other threads:[~2019-10-06 11:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 21:53 Skip Tavakkolian
2019-10-05 1:41 ` Sean Hinchee
2019-10-06 11:09 ` Richard Miller [this message]
2019-10-07 3:54 ` Skip Tavakkolian
2019-10-07 7:46 ` David du Colombier
2019-10-07 8:36 ` Lucio De Re
2019-10-11 16:26 ` Jerome Ibanes
2019-10-16 16:01 ` Juan Cuzmar
2019-10-17 1:58 ` Sean Hinchee
2019-10-17 2:07 ` Juan Cuzmar
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=2eb38428179796cbf729751c27edbdb9@hamnavoe.com \
--to=9fans@hamnavoe.com \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).