9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] go under plan9 on the radpberry pi?
Date: Fri, 20 Sep 2019 09:43:00 +0100	[thread overview]
Message-ID: <219d633c491c593eafe8c551f142751d@hamnavoe.com> (raw)
In-Reply-To: <20190919224632.33A4A1570CEA@mail.bitblocks.com>

> Only lightly tested.

In a sense, plan9/arm go is tested as well as any other platform:
under the go continuous development process, every time a change
is made to the compiler or runtime library, a complete test suite
is run on builder machines for every supported architecture and
operating system.  If you look at https://build.golang.org and
scroll wayyyyyyyy over to the right, the plan9/arm column refers
to a set of Raspberry Pi machines run by David du Columbier and me.

In another sense, it's probably not very well tested at all:
I'm not aware of any production application being run on go in
Plan 9, on any machine architecture.  I haven't used go seriously
myself, but I find the test suite gives the OS such a brutal workout
(especially with small physical memory) that it's a good way
to flush out underlying Plan 9 bugs.

The tests show some intermittent hard-to-reproduce failures ("flakes")
on all the Plan 9 builders.  Many are timing issues because the tests
make assumptions about absolute speed of builder machines; but there
are some "can't happen" panics during garbage collection which smell
like a cache or memory barrier problem.  Please don't use plan9/arm
go to run your nuclear power plant just yet ...




  parent reply	other threads:[~2019-09-20  8:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-19 21:41 Steve Simon
2019-09-19 22:46 ` Bakul Shah
2019-09-19 23:15   ` Michael Misch
2019-09-20  3:26     ` Matthew Veety
2019-09-20  4:37       ` Lyndon Nerenberg
2019-09-20  5:29         ` Steve Simon
2019-09-20  5:32           ` Michael Misch
2019-09-20  6:07           ` Bakul Shah
2019-09-20  8:53             ` Richard Miller
2019-09-21  1:23               ` Bakul Shah
2019-09-21 12:31                 ` hiro
2019-09-21 23:55                   ` Bakul Shah
2019-09-20  8:43   ` Richard Miller [this message]
2019-09-20 17:10     ` Steve Simon

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=219d633c491c593eafe8c551f142751d@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).