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

cmd/internal/testdir: unrecognized failures #63885

Closed
gopherbot opened this issue Nov 1, 2023 · 5 comments
Closed

cmd/internal/testdir: unrecognized failures #63885

gopherbot opened this issue Nov 1, 2023 · 5 comments
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Milestone
Backlog

Comments

@gopherbot
Copy link 

#!watchflakes
default <- pkg == "cmd/internal/testdir" && test == ""

Issue created automatically to collect these failures.

Example (log):

2023/11/01 20:21:22 exit status 1

— 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 Nov 1, 2023
@gopherbot
Copy link
Author

Found new dashboard test flakes for:

#!watchflakes
default <- pkg == "cmd/internal/testdir" && test == ""
2023-11-01 19:04 linux-ppc64le-buildlet go@ea3010d9 cmd/internal/testdir (log) 
2023/11/01 20:21:22 exit status 1

— watchflakes

@bcmills bcmills added the compiler/runtime Issues related to the Go compiler and/or runtime. label Nov 1, 2023
@mknyszek
Copy link
Contributor

mknyszek commented Nov 8, 2023

There's really nothing to go off of here... Oof. I guess we'll wait for more failures?

CC @golang/ppc64

@mknyszek mknyszek added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Nov 8, 2023
@mknyszek mknyszek added this to the Backlog milestone Nov 8, 2023
@mknyszek
Copy link
Contributor

mknyszek commented Nov 8, 2023

In triage, this makes me think it could be a crash in a signal handler causing an immediate process death.

@laboger
Copy link
Contributor

laboger commented Nov 21, 2023

It's hard to say what this was with the minimal failure output that is given in the log. Usually something like that is due to something odd happening in the environment, commonly due to a OOM from what I remember.

There was this change https://go-review.googlesource.com/c/go/+/541635 that fixed some failures in testdir tests but the failure output was different.

@gopherbot
Copy link
Author

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.)

@gopherbot gopherbot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Projects
Test Flakes
Status: Done
Milestone
Backlog
Development

No branches or pull requests
4 participants
@mknyszek @bcmills @gopherbot @laboger