From: Bakul Shah <bakul@iitbombay.org>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] amd64 bootstrap file fo go1.16.3
Date: Wed, 21 Apr 2021 07:27:44 -0700 [thread overview]
Message-ID: <EA034FF5-E442-419F-9EC3-C8714CD1F90C@iitbombay.org> (raw)
In-Reply-To: <54a436c2d5fc4d7af2fdc9734c3869e4@hamnavoe.com>
On Apr 21, 2021, at 2:41 AM, Richard Miller <9fans@hamnavoe.com> wrote:
>
>
>> go tool dist: Failed: exit status: 'go 6839: 1'
>> all.rc 165: go 6566: 1
>> =======to here======
>> It took about half a day to accomplish!
>
> Some things that can make go tools and test suite quicker:
> - use ramfs for /tmp
> - use a local file server, with local disk or aoe on a fast connection
> - make sure you have lots of RAM, or swap to a local disk
I saw a lot of failures in go’s own test suite run via all.rc. This was
on 9front/amd64 under the bhyve hypervisor on freebsd. I gave
the VM 4GB and two cores so resource constraint should not be an
issue. Is there a list of known to fail tests? Thanks.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T75ee4ccd407669dd-Mf8ae307dfd776ec0fe3cbed2
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2021-04-21 14:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-18 0:28 kokamoto
2021-04-18 4:05 ` kokamoto
2021-04-18 8:36 ` Philip Silva via 9fans
2021-04-18 22:36 ` kokamoto
2021-04-19 23:02 ` kokamoto
2021-04-20 7:24 ` David du Colombier
2021-04-20 23:03 ` kokamoto
2021-04-27 6:00 ` kokamoto
2021-04-27 7:01 ` David du Colombier
2021-04-21 9:39 ` Richard Miller
2021-04-21 14:27 ` Bakul Shah [this message]
2021-04-21 15:04 ` Richard Miller
2021-04-20 23:05 ` kokamoto
2021-04-21 5:23 ` kokamoto
2021-04-21 6:56 ` David du Colombier
2021-04-21 9:20 ` kokamoto
2021-04-21 9:29 ` Richard Miller
2021-04-21 11:04 ` kokamoto
2021-04-18 9:08 ` David du Colombier
2021-04-18 10:19 ` kokamoto
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=EA034FF5-E442-419F-9EC3-C8714CD1F90C@iitbombay.org \
--to=bakul@iitbombay.org \
--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).