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.

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

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.

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

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

Oof. I'll add the skip.

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

Ah OK. Feel free to send it to me.

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