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

runtime: TestLockOSThreadExit failures #70095

Open
gopherbot opened this issue Oct 29, 2024 · 3 comments
Open

runtime: TestLockOSThreadExit failures #70095

gopherbot opened this issue Oct 29, 2024 · 3 comments
Labels
arch-riscv Issues solely affecting the riscv64 architecture. 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.
Milestone
Backlog

Comments

@gopherbot
Copy link
Contributor 

#!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 gopherbot added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Oct 29, 2024
@gopherbot
Copy link
Contributor Author

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

@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Oct 29, 2024
@mknyszek
Copy link
Contributor

@golang/riscv64

@mknyszek mknyszek added this to the Backlog milestone Oct 30, 2024
@mknyszek mknyszek added the arch-riscv Issues solely affecting the riscv64 architecture. label Oct 30, 2024
@mengzhuo
Copy link
Contributor

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
arch-riscv Issues solely affecting the riscv64 architecture. 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.
Projects
Go Compiler / Runtime
Status: Todo
Test Flakes
Status: No status
Milestone
Backlog
Development

No branches or pull requests
3 participants
@mengzhuo @mknyszek @gopherbot