-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
cmd/go: panic: LoadImport called with empty package path [recovered] when building source #67984
Comments
Similar to #60230 |
Similar Issues
(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.) |
I tried, with a very similar configuration (Darwin-amd64, using 1.22.4 as the building compiler, building at tip, similar settings in goenv), but could not reproduce. |
It doesn’t always reproduce for me. I’ve tried it several times since filing the issue. |
As stated in the OP, I compared the build times of two versions of source, one which I altered, one which I didn't. In case there's a possibility that I misreported which one failed, the alteration to the source that I made resulted in the following pull request, which obviously can't be responsible for the type of failure reported in this issue. https://go-review.googlesource.com/c/go/+/592735 |
@MikeMitchellWebDev at which commit were you running make.bash? I understand the build doesn't fail reliably, but are you still able to reproduce occasionally? |
I was running make.bash at |
I tried running make.bash at If we could get reproduction instructions that will cause the failures to happen, say, once in every five or so attempts, if not consistently, that would be useful for us to diagnose and fix. |
Timed out in state WaitingForInfo. Closing. (I am just a bot, though. Please speak up if this is a mistake or you have the requested information.) |
Go version
go version go1.22.0 darwin/amd64
Output of
go env
in your module/workspace:What did you do?
I tried to time how long it takes to build the Go source code (which I didn't alter at all) by running
time ./make.bash
from thesrc
dir of the repository as the Go blog instructs. The first time it built successfully, and then I ran the same build command two other times and the build process failed each timeOn another version of the Go source code (which I had, incidentally, altered minimally) running
time ./make.bash
ran successfully two times in a row.What did you see happen?
1st time
2nd time
What did you expect to see?
I expected the build to run successfully each time (as it did on the source code that I did alter)
The text was updated successfully, but these errors were encountered: