You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From all.bash on my laptop. I have CLs pending but nothing in runtime, and this crash is before any user code starts. Up to date as of:
$ git log -n1 $(git codereview branchpoint)
commit 590fce48849cc7f81b890d6e9b6120fc6681e19a
Author: Nigel Tao <nigeltao@golang.org>
AuthorDate: Sat Oct 29 13:23:50 2016 +1100
Commit: Nigel Tao <nigeltao@golang.org>
CommitDate: Sun Oct 30 22:52:14 2016 +0000
compress/flate: tighten the BestSpeed max match offset bound.
The problem is that none of the line numbers match up with my current sources. This is the kind of failure I saw when working on the Go 1.7 release branch in a different client, before I had all the Sierra fixes patched in. I wonder if somehow there is a bad binary that is not being rebuilt properly during the test.
The text was updated successfully, but these errors were encountered:
It looks like I managed to run 'go install' in the gopl.io/ch11/echo directory at some point. That binary was stale (pre-Sierra), causing the pre-Sierra-like crash. Deleted ~/bin/echo and all is well.
From all.bash on my laptop. I have CLs pending but nothing in runtime, and this crash is before any user code starts. Up to date as of:
Failure:
The problem is that none of the line numbers match up with my current sources. This is the kind of failure I saw when working on the Go 1.7 release branch in a different client, before I had all the Sierra fixes patched in. I wonder if somehow there is a bad binary that is not being rebuilt properly during the test.
The text was updated successfully, but these errors were encountered: