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

x/crypto/acme: TestRFC_WaitOrderError failures #57106

Closed
gopherbot opened this issue Dec 6, 2022 · 3 comments
Closed

x/crypto/acme: TestRFC_WaitOrderError failures #57106

gopherbot opened this issue Dec 6, 2022 · 3 comments
Labels
FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Unreleased

Comments

@gopherbot
Copy link 

#!watchflakes
post <- pkg == "golang.org/x/crypto/acme" && test == "TestRFC_WaitOrderError"

Issue created automatically to collect these failures.

Example (log):

--- FAIL: TestRFC_WaitOrderError (3.00s)
    rfc8555_test.go:921: WaitOrder took too long to return

— 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 Dec 6, 2022
@gopherbot
Copy link
Author

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "golang.org/x/crypto/acme" && test == "TestRFC_WaitOrderError"
2022-11-17 19:18 darwin-amd64-11_0 crypto@2c476679 go@e727f419 x/crypto/acme.TestRFC_WaitOrderError (log) 
--- FAIL: TestRFC_WaitOrderError (3.00s)
    rfc8555_test.go:921: WaitOrder took too long to return

— watchflakes

@gopherbot gopherbot added this to the Unreleased milestone Dec 6, 2022
@bcmills
Copy link
Contributor

bcmills commented Dec 6, 2022

Like #57107 and #57105, this appears to be caused by a hard-coded timeout in the test.

@bcmills
Copy link
Contributor

bcmills commented Dec 6, 2022

Duplicate of #57107

@bcmills bcmills marked this as a duplicate of #57107 Dec 6, 2022
@bcmills bcmills closed this as not planned Won't fix, can't repro, duplicate, stale Dec 6, 2022
@golang golang locked and limited conversation to collaborators Dec 6, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
None yet
Milestone
Unreleased
Development

No branches or pull requests
2 participants
@bcmills @gopherbot