Skip to content
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.

Sign up for GitHub

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

Jump to bottom

net: TestVariousDeadlines failures #66039

Open
gopherbot opened this issue Feb 29, 2024 · 2 comments
Open

net: TestVariousDeadlines failures #66039

gopherbot opened this issue Feb 29, 2024 · 2 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 

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

Issue created automatically to collect these failures.

Example (log):

--- FAIL: TestVariousDeadlines (39.58s)
    timeout_test.go:1006: 1ns 0/1
    timeout_test.go:1022: 1ns 0/1: good timeout after 10.811µs; 0 bytes
    timeout_test.go:1006: 2ns 0/1
    timeout_test.go:1022: 2ns 0/1: good timeout after 10.534µs; 0 bytes
    timeout_test.go:1006: 5ns 0/1
    timeout_test.go:1010: dial tcp 127.0.0.1:51510: connect: operation timed out

— 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 Feb 29, 2024
@gopherbot
Copy link
Author

Found new dashboard test flakes for:

#!watchflakes
default <- pkg == "net" && test == "TestVariousDeadlines"
2024-02-29 18:51 darwin-amd64-13 go@adc575e6 net.TestVariousDeadlines (log) 
--- FAIL: TestVariousDeadlines (39.58s)
    timeout_test.go:1006: 1ns 0/1
    timeout_test.go:1022: 1ns 0/1: good timeout after 10.811µs; 0 bytes
    timeout_test.go:1006: 2ns 0/1
    timeout_test.go:1022: 2ns 0/1: good timeout after 10.534µs; 0 bytes
    timeout_test.go:1006: 5ns 0/1
    timeout_test.go:1010: dial tcp 127.0.0.1:51510: connect: operation timed out

— watchflakes

@bcmills
Copy link
Contributor

bcmills commented Feb 29, 2024 •
edited

(attn @dneil @ianlancetaylor)

Possibly related to @rsc's recent runtime timer changes, and/or the ongoing issues with darwin-amd64 builders?

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

No branches or pull requests
2 participants
@bcmills @gopherbot