> 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 ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T80ee3327f2f3dc57-Mbb1bd4efca6ee049b840ebb3 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
