runtime: TestLockOSThreadExit failures

[gopherbot]

#!watchflakes
default <- pkg == "runtime" && test == "TestLockOSThreadExit"

Issue created automatically to collect these failures.

Example (log):

=== RUN   TestLockOSThreadExit
    proc_test.go:983: /home/swarming/.swarming/w/ir/x/t/go-build3157675313/testprog.exe LockOSThreadMain (36.043549ms): ok
    proc_test.go:989: /home/swarming/.swarming/w/ir/x/t/go-build3157675313/testprog.exe LockOSThreadAlt (31.099939ms): ok
    proc_test.go:991: want "OK\n", got "error: read /proc/self/task/3378684/status: no such process\n"
--- FAIL: TestLockOSThreadExit (0.07s)

— watchflakes

[gopherbot]

Found new dashboard test flakes for:

#!watchflakes
default <- pkg == "runtime" && test == "TestLockOSThreadExit"

2024-10-22 16:16 gotip-linux-riscv64 go@4e702586 runtime.TestLockOSThreadExit (log)

=== RUN   TestLockOSThreadExit
    proc_test.go:983: /home/swarming/.swarming/w/ir/x/t/go-build3157675313/testprog.exe LockOSThreadMain (36.043549ms): ok
    proc_test.go:989: /home/swarming/.swarming/w/ir/x/t/go-build3157675313/testprog.exe LockOSThreadAlt (31.099939ms): ok
    proc_test.go:991: want "OK\n", got "error: read /proc/self/task/3378684/status: no such process\n"
--- FAIL: TestLockOSThreadExit (0.07s)

— watchflakes

[mknyszek]

@golang/riscv64

[mengzhuo]

I run runtime test at 6d39245

=== CONT  TestCgoLockOSThreadExit                                                                                     
    crash_test.go:169: running /home/mzh/godev/bin/go build -o /tmp/go-build111803402/testprogcgo.exe                 
    crash_test.go:191: built testprogcgo in 49.162866263s                                                             
    proc_test.go:983: /tmp/go-build111803402/testprogcgo.exe LockOSThreadMain (25.456336ms): ok                       
    proc_test.go:989: /tmp/go-build111803402/testprogcgo.exe LockOSThreadAlt (23.514387ms): ok                        
--- PASS: TestCgoLockOSThreadExit (49.21s)                                                                            
PASS                                                                                                                  
ok      runtime 93.335s

Flaky?

[limeidan]

I also encountered this problem when doing local testing of loong64, but it cannot be reproduce stably. We will continue to test and track it.