-
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
net: TestLookupPTR failures on windows-amd64-longtest builder #38111
Comments
There are at least two different failure modes:
|
Still ongoing at a low rate:
|
One more this week. The @ianlancetaylor, @bradfitz: could you double-check whether something relating to the
|
Note that the |
Most of the errors are of the form
The test actually runs the There are also some errors in which the |
Change https://go.dev/cl/414634 mentions this issue: |
For #38111 Change-Id: I2651687367af68ee070ea91106f4bc18adab2762 Reviewed-on: https://go-review.googlesource.com/c/go/+/414634 Reviewed-by: Ian Lance Taylor <[email protected]> Reviewed-by: Bryan Mills <[email protected]> Run-TryBot: Ian Lance Taylor <[email protected]> Auto-Submit: Ian Lance Taylor <[email protected]> TryBot-Result: Gopher Robot <[email protected]>
For golang#38111 Change-Id: I2651687367af68ee070ea91106f4bc18adab2762 Reviewed-on: https://go-review.googlesource.com/c/go/+/414634 Reviewed-by: Ian Lance Taylor <[email protected]> Reviewed-by: Bryan Mills <[email protected]> Run-TryBot: Ian Lance Taylor <[email protected]> Auto-Submit: Ian Lance Taylor <[email protected]> TryBot-Result: Gopher Robot <[email protected]>
https://storage.googleapis.com/go-build-log/a47db80f/windows-amd64-longtest_2ecbeb5f.log:
|
(CC @golang/windows) |
Change https://go.dev/cl/427915 mentions this issue: |
For #38111. Change-Id: I43bdd756bde0adcd156cf9750b49b3b989304df7 Reviewed-on: https://go-review.googlesource.com/c/go/+/427915 Reviewed-by: Ian Lance Taylor <[email protected]> TryBot-Result: Gopher Robot <[email protected]> Auto-Submit: Bryan Mills <[email protected]> Run-TryBot: Bryan Mills <[email protected]>
Another recent flake: |
Found new dashboard test flakes for:
2022-07-29 22:09 windows-amd64-longtest go@9a2001a8 net.TestLookupPTR (log)
2022-08-17 16:26 windows-amd64-longtest go@014f0e82 net.TestLookupPTR (log)
2022-08-26 18:28 windows-amd64-longtest go@bf812b32 net.TestLookupPTR (log)
2022-08-31 15:30 windows-amd64-longtest go@d01200e7 net.TestLookupPTR (log)
2022-08-31 16:59 windows-amd64-longtest go@0d6a7f9d net.TestLookupPTR (log)
2022-09-02 02:09 windows-amd64-longtest go@a31c062c net.TestLookupPTR (log)
|
This may be fixed by CL 462051. |
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.) |
It's not obvious to me whether the test is flaky, the builder has a flaky network connection, or the test is detecting something that is actually wrong.
CC @mikioh @bradfitz @ianlancetaylor (for
net
), @dmitshur, @toothrot, @cagedmantis, @andybons (for builders)2020-03-26T17:48:20-918d4d4/windows-amd64-longtest
2020-03-06T14:41:22-2b0f481/windows-amd64-longtest
2020-01-09T18:00:06-8ac98e7/windows-amd64-longtest
2019-12-30T09:34:53-4b43700/windows-amd64-longtest
2019-11-13T08:07:51-bf5f641/windows-amd64-longtest
The text was updated successfully, but these errors were encountered: