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] Re: various problems with installing go lang
Date: Wed, 28 Oct 2020 13:08:14 +0000	[thread overview]
Message-ID: <f325c59b1f090e8e83c8e8d67ea2d8fd@hamnavoe.com> (raw)
In-Reply-To: <f3063557-b6a5-49c7-99d3-312b91482c48@www.fastmail.com>

> non-deterministic builder

It's probably not non-deterministic. It's just unpredictable (to me)
because the rules are encoded in the logic of 'go build' rather than
being visibly exposed as mk patterns. I suspect I'm not the only one
who doesn't find the staleness algorithm predictable, as evidenced
by the number of times 'go tool dist test' for a single package
repeatedly tries to rebuild the toolchain and standard library and
hen re-check for staleness, even when invoked with '-no-rebuild'.

See https://github.com/golang/go/issues/24300


  reply	other threads:[~2020-10-28 13:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-24  4:15 nydldmcd2
2020-10-24  4:44 ` [9fans] " Nick Owens
2020-10-24  5:32   ` nydldmcd2
2020-10-24  5:39     ` Nick Owens
2020-10-24 14:38     ` Fazlul Shahriar
2020-10-24  5:29 ` nydldmcd2
2020-10-24 14:15   ` [9fans] " Pavel Renev
2020-10-24 20:59     ` ori
2020-10-27 23:45   ` nydldmcd2
2020-10-28  9:46     ` [9fans] " Richard Miller
2020-10-28 11:00       ` Ethan Gardener
2020-10-28 13:08         ` Richard Miller [this message]
2020-10-28 16:13           ` Ethan Gardener
2020-10-30  2:34             ` nydldmcd2
2020-10-30  9:43               ` Richard Miller
2020-11-01 19:43                 ` nydldmcd2
2020-11-02 16:03                   ` ori
2021-03-10 17:25                     ` ejh
2020-11-01 19:43                 ` nydldmcd2

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