-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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
net: re-enable or delete TestLookupLongTXT #22857
Comments
It seems the Plan 9 DNS resolver (
|
Change https://golang.org/cl/79695 mentions this issue: |
CL 79555 added TestLookupLongTXT. However, this test is failing on Plan 9, because the DNS resolver (ndb/dns) only returns a single TXT record. Updates #22857. Change-Id: I33cdc63a3d3de4d1c7f2684934316c44992fb9e2 Reviewed-on: https://go-review.googlesource.com/79695 Run-TryBot: David du Colombier <0intro@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
@0intro, feel free to send plan9 fixes whenever, but I'm removing this from Go1.10. If the fix only touches plan9 stuff, I'm comfortable taking it even late in the cycle. |
Different, potentially related failure: https://storage.googleapis.com/go-build-log/d38832a2/linux-amd64_b2d10b95.log
This happened on an unrelated CL, https://go-review.googlesource.com/c/go/+/77253 - |
This isn't just a plan9 issue. It's failing all over the place. @ianlancetaylor and @rsc were discussing the problem recently. I think they understand what's happening here. Ian, can you summarize? /cc @mikioh |
Change https://golang.org/cl/97416 mentions this issue: |
I don't actually understand what is going on here. Maybe @rsc does. It seems to have something to do with how caches handle multiple TXT records. |
Flaky tests failing trybots help nobody. Updates #22857 Change-Id: I87bc018651ab4fe02560a6d24c08a1d7ccd8ba37 Reviewed-on: https://go-review.googlesource.com/97416 Reviewed-by: Ian Lance Taylor <iant@golang.org>
This code was rewritten as part of #21160. We should try enabling the test again at the start of the 1.13 cycle. |
See also #23873. |
This issue is currently labeled as early-in-cycle for Go 1.19. |
@neild This is another |
To summarize: TestLookupLongTXT was disabled a long time ago because it was flaky. The underlying code has since been rewritten. We should reenable the test to see if it's fixed now. This should have been enabled early in the 1.19 cycle. It's now late in the 1.19 cycle. Kicking back to 1.20. |
This issue is currently labeled as early-in-cycle for Go 1.20. |
Change https://go.dev/cl/423454 mentions this issue: |
Looks like the same issue as described in #22857 (comment) is still occurring: |
Change https://go.dev/cl/424535 mentions this issue: |
Test is still flaky. For #22857 Change-Id: Ic0d979778eb4c2d3779b18a983e7077789ae08a4 Reviewed-on: https://go-review.googlesource.com/c/go/+/424535 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Damien Neil <dneil@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
CL 79555 added TestLookupLongTXT. This test is failing on Plan 9.
See https://build.golang.org/log/d83b9b31e94b0b5093c0d2813f78105531e8de3e
The text was updated successfully, but these errors were encountered: