Skip to content

net: TestFilePacketConn failures #73698

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

Closed
gopherbot opened this issue May 13, 2025 · 3 comments
Closed

net: TestFilePacketConn failures #73698

gopherbot opened this issue May 13, 2025 · 3 comments
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.

Comments

@gopherbot
Copy link
Contributor

#!watchflakes
default <- pkg == "net" && test == "TestFilePacketConn"

Issue created automatically to collect these failures.

Example (log):

=== RUN   TestFilePacketConn
    file_test.go:273: file file+net udp4:127.0.0.1:62481->: invalid argument
--- FAIL: TestFilePacketConn (0.00s)

watchflakes

@gopherbot
Copy link
Contributor Author

Found new dashboard test flakes for:

#!watchflakes
default <- pkg == "net" && test == "TestFilePacketConn"
2025-05-13 17:01 gotip-windows-amd64-longtest go@4aeb9ba0 net.TestFilePacketConn (log)
=== RUN   TestFilePacketConn
    file_test.go:273: file file+net udp4:127.0.0.1:62481->: invalid argument
--- FAIL: TestFilePacketConn (0.00s)

watchflakes

@gopherbot gopherbot added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label May 13, 2025
@mknyszek
Copy link
Contributor

Looking at the test history the first recorded instance appears to be https://ci.chromium.org/ui/p/golang/builders/ci/gotip-windows-amd64-longtest/b8714968133031208929/test-results?sortby=&groupby= and it also appears to be Windows specific. The nearest commit before the first failure that looks related is 41bd52b which deals with files and sockets on Windows. Just a guess though, I could be wrong. CC @qmuntal @neild

@qmuntal
Copy link
Member

qmuntal commented May 15, 2025

Thanks for the hints @mknyszek. The failure mode looks similar to #73683, which have just been closed by https://go.dev/cl/672195. I'll mark this issue as closed, given that that it will probable be fixed by CL 672195.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
Status: Done
Development

No branches or pull requests

3 participants