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
heschi opened this issue
Jan 18, 2019
· 2 comments
Labels
NeedsFixThe path to resolution is known, but the work has not been done.TestingAn issue that has been verified to require only test changes, not just a test failure.ToolsThis label describes issues relating to any tools in the x/tools repository.
bradfitz
added
Testing
An issue that has been verified to require only test changes, not just a test failure.
NeedsFix
The path to resolution is known, but the work has not been done.
labels
Jan 18, 2019
panic: runtime error: index out of range [recovered]
panic: runtime error: index out of range
goroutine 439 [running]:
testing.tRunner.func1(0x12810000)
C:/workdir/go/src/testing/testing.go:830 +0x30e
panic(0x69a260, 0x90df70)
C:/workdir/go/src/runtime/panic.go:532 +0x165
golang.org/x/tools/go/packages_test.testParseFileModifyAST(0x12810000, 0x740990, 0x92489c)
C:/workdir/gopath/src/golang.org/x/tools/go/packages/packages_test.go:810 +0x3d7
golang.org/x/tools/go/packages/packagestest.TestAll.func1(0x12810000)
C:/workdir/gopath/src/golang.org/x/tools/go/packages/packagestest/export.go:99 +0x51
testing.tRunner(0x12810000, 0x12776140)
C:/workdir/go/src/testing/testing.go:865 +0x97
created by testing.(*T).Run
C:/workdir/go/src/testing/testing.go:916 +0x2b2
FAIL golang.org/x/tools/go/packages 26.424s
NeedsFixThe path to resolution is known, but the work has not been done.TestingAn issue that has been verified to require only test changes, not just a test failure.ToolsThis label describes issues relating to any tools in the x/tools repository.
https://build.golang.org/log/60aa789811bdedb1697255f1dee30adb917d3f0c
https://build.golang.org/log/ede332848726e7af41109fe3ebc7e813e58f7ab8
https://storage.googleapis.com/go-build-log/dc889025/windows-amd64-2016_fed5c8f5.log
example:
The text was updated successfully, but these errors were encountered: