-
Notifications
You must be signed in to change notification settings - Fork 18k
go/internal/gccgoimporter: TestInstallationImporter failing on SmartOS #29006
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
CC @thanm |
Hmm, gomote shows that gccgo 4.7.4 is installed. That is from 2012. Interesting that it works this well, really. |
Building GCC 4.7 to see if I can reproduce the problem locally. |
Thanks Ian. |
GCC 4.7 is old enough that it doesn't build with GCC 7, this looks like fun.... |
I am willing to take a look. Is it relatively easy to to upload files from a builder via gomote? I can just transfer the *.gox files from the installation back to my workstation. |
|
I have the failing .gox file now. |
The export data is:
|
Looks like it started failing when Than fixed the test to actually run gccgo, so this may have been failing for a long time. |
Thanks. I'll pick at it to see if I can determine what's going on -- I should be able to just incorporate the blob you uploaded into a test. |
It looks like the offending blob is
What's happening is that we start named type 75, whose underlying type is 76 (a struct), however before 76 has been completed, there is a reference back to 75:
|
Change https://golang.org/cl/151997 mentions this issue: |
That specific problem is fixed but the general problem is not fixed. https://build.golang.org/log/bd6c332435b220601a329d5d7566fada4ee29ac5 |
Rats. Thanks for picking up on that; I will investigate. |
I'm about to send a CL for the bad packages. |
Change https://golang.org/cl/152077 mentions this issue: |
Oh, these failures are uninteresting. The other failure is that the old gccgo can't read type alias information, which is unsurprising. |
I'll send a fix. |
Change https://golang.org/cl/152078 mentions this issue: |
TestInstallationImporter checks that it can read the export data for a list of known standard library packages. It was failing on the SmartOS builder which has GCC 4.7 installed. Skip packages that did not exist in GCC 4.7. Most packages are still there and the missing packages are fairly simple, so this doesn't really affect test quality. Updates #29006 Change-Id: If7ae6f83d51d40168a9692acb0b99c9bf21f2a4d Reviewed-on: https://go-review.googlesource.com/c/152077 Run-TryBot: Ian Lance Taylor <iant@golang.org> Reviewed-by: Than McIntosh <thanm@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org>
Seems to be a consistent failure. Example: https://build.golang.org/log/52004d2ece81d2342a5810c4d29c264e6a0c8e81
CC: @griesemer @ianlancetaylor
The text was updated successfully, but these errors were encountered: