-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/go: internal/modload TestImport stuck in infinite loop(?) #27080
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
Every time we fix a long test, there's another one popping up :) Hopefully we'll have linux-amd64-longtest green soon. |
Change https://golang.org/cl/129778 mentions this issue: |
That's how you know the longtest builder is doing its job :^) |
Now we just need brave heroes to do the same work with darwin and windows longtest builders. |
Change https://golang.org/cl/130275 mentions this issue: |
It is possible to enter the parent-walking directory loop in a way that it will loop forever - if mdir is empty, and d reaches ".". To avoid this, make sure that the 'd = filepath.Dir(d)' step only happens if the parent directory is actually different than the current directory. This fixes some of the tests like TestImport/golang.org_x_net_context, which were never finishing before. While at it, also fix TestImport/golang.org_x_net, which seems to have the wrong expected error. The root of the x/net repo doesn't have a go.mod file, nor is part of a module itself, so it seems like the expected error should reflect that. After these two changes, 'go test cmd/go/internal/modload' passes on my linux/amd64 machine. Fixes #27080. Change-Id: Ie8bab0f9fbc9f447844cbbc64117420d9087db1b Reviewed-on: https://go-review.googlesource.com/129778 Run-TryBot: Daniel Martí <mvdan@mvdan.cc> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> (cherry picked from commit 692307a) Reviewed-on: https://go-review.googlesource.com/130275 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> Reviewed-by: Andrew Bonventre <andybons@golang.org>
and then it's stuck there, spinning at 100% cpu. I've let it run for about an hour on my machine, and it didn't finish. On the longtest builder it times out, and there's a stacktrace:
https://build.golang.org/log/8b2c6c726faf3a87bc5862a0e3192d66df682810
The text was updated successfully, but these errors were encountered: