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.

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

runtime: TestGdbBacktrace failures with "No such process." since 2021-10-15 #50838

Closed
bcmills opened this issue Jan 26, 2022 · 9 comments
Closed

runtime: TestGdbBacktrace failures with "No such process." since 2021-10-15 #50838

bcmills opened this issue Jan 26, 2022 · 9 comments
Labels
NeedsInvestigation release-blocker
Milestone

Comments

@bcmills
Copy link
Member

@bcmills bcmills commented Jan 26, 2022

greplogs --dashboard -md -l -e 'FAIL: TestGdbBacktrace .*(?:\n .*)*: No such process\.'

2022-01-24T17:07:30-f88c3b9/linux-386
2021-11-05T20:59:43-dbd3cf8/linux-amd64-nocgo
2021-10-15T03:49:17-8dab959/linux-amd64-nocgo

This is a new failure mode for a known-flaky test (see #37405; CC @aclements, @jeremyfaller). Unfortunately, this failure mode appears to predate the CLs added for that issue.

@mknyszek mknyszek added the NeedsInvestigation label Jan 27, 2022
@mknyszek mknyszek added this to the Backlog milestone Jan 27, 2022
@mknyszek
Copy link
Contributor

@mknyszek mknyszek commented Jan 27, 2022

Since this failure mode is old, I'm putting this in backlog. But if it looks like this is plaguing the dashboard enough, we might want to consider moving it into the 1.18 milestone.

@bcmills
Copy link
Member Author

@bcmills bcmills commented Jan 27, 2022

Since this failure mode is old,

Note that this particular failure mode is not old — it's new as of October. (The older failures for this test have different failure modes.)

@bcmills
Copy link
Member Author

@bcmills bcmills commented Feb 11, 2022

One more:

greplogs --dashboard -md -l -e 'FAIL: TestGdbBacktrace .*(?:\n .*)*: No such process\.' --since=2022-01-26

2022-02-10T01:08:52-656d3f4/linux-386

Note that these failures are so far all on first-class ports.

@bcmills bcmills removed this from the Backlog milestone Feb 11, 2022
@bcmills bcmills added this to the Go1.18 milestone Feb 11, 2022
@bcmills
Copy link
Member Author

@bcmills bcmills commented Feb 11, 2022

This is a release blocker at least until a skip is added for this failure mode, then it can be moved back to the backlog.

(Given the other failure modes of this test, I don't think it's worth trying to get in a fix for the root cause during the freeze.)

@bcmills
Copy link
Member Author

@bcmills bcmills commented Feb 11, 2022

This looks like https://sourceware.org/bugzilla/show_bug.cgi?id=9086, open against gdb since 2005-08-03. 😩

@mknyszek
Copy link
Contributor

@mknyszek mknyszek commented Feb 11, 2022

Oof. I'll add the skip.

@bcmills
Copy link
Member Author

@bcmills bcmills commented Feb 11, 2022

I've got a CL pending already. I should also update the other skip with a comment for the GDB bug...

@mknyszek
Copy link
Contributor

@mknyszek mknyszek commented Feb 11, 2022

Ah OK. Feel free to send it to me.

@gopherbot
Copy link

@gopherbot gopherbot commented Feb 11, 2022

Change https://go.dev/cl/385175 mentions this issue: runtime: update TestGdbBacktrace skips for known GDB bugs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NeedsInvestigation release-blocker
Projects
None yet
Development

No branches or pull requests

3 participants