Michael Knyszek

Alrighty, this is affecting quite a few people. Unassigning so it goes back in the triage queue.

To be clear, I'm not saying that we're necessarily going to make this a supported build configuration, but we should figure out what we're going to do. @clarkmcc Unfortunately, that...

It seems this has missed 2 releases. Moving to backlog. Please comment if you plan to work on it in Go 1.22 and I'm happy to move it there. Thanks!

@codablock Sorry, somehow I totally missed your comment from back in November. That sounds like a different issue (this seems pretty Windows-specific; ~there's Windows syscall callback functionality that doesn't exist...

Actually, looking at the goroutine dump earlier on, this looks like an issue I've seen before. I think it was around Go 1.17 as well, and I think we fixed...

> Everyone seems to be ignoring my reply (which was merely to call out my post from 2022-09-21), but if he thinks it was fixed during the 1.17 release cycle......

Filed #59576 to track any failures we see on our builders. It's closed right now on purpose; if we see any failures the bot will open the issue and we'll...

These tests do invoke the compiler, but only on very small programs. Still, if that's a problem, I can restructure the tests to group all the programs together like `src/runtime/testdata/testprog`....

Woooaaah... that is way longer than that test should ever take. That could be a deadlock, perhaps. I'll try to reproduce.

@prattmic Since this only happened twice on Darwin LUCI machines, do you think there's a chance this is related to some of the recent machine instability on LUCI? Thanks.