Skip to content

runtime: TestLockOSThreadExit failures #65736

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
Closed
gopherbot opened this issue Feb 15, 2024 · 2 comments
Closed

runtime: TestLockOSThreadExit failures #65736

gopherbot opened this issue Feb 15, 2024 · 2 comments
Assignees
@mknyszek
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.

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-build4249258931/testprog.exe LockOSThreadMain (3.989747ms): ok
    proc_test.go:989: /home/swarming/.swarming/w/ir/x/t/go-build4249258931/testprog.exe LockOSThreadAlt: exit status 2
    proc_test.go:991: want "OK\n", got "panic: runtime error: index out of range [2] with length 0\n\ngoroutine 1 [running]:\nmain.tidExists(0xba?)\n\t/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/testdata/testprog/syscalls_linux.go:25 +0xdd\nmain.LockOSThreadAlt()\n\t/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/testdata/testprog/lockosthread.go:93 +0x185\nmain.main()\n\t/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/testdata/testprog/main.go:34 +0x133\n"
--- FAIL: TestLockOSThreadExit (0.02s)

— 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 Feb 15, 2024
@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Feb 15, 2024
@gopherbot
Copy link
Contributor Author

Found new dashboard test flakes for:

#!watchflakes
default <- pkg == "runtime" && test == "TestLockOSThreadExit"
2024-02-14 18:18 gotip-linux-amd64-newinliner go@b19164d5 runtime.TestLockOSThreadExit (log) 
=== RUN   TestLockOSThreadExit
    proc_test.go:983: /home/swarming/.swarming/w/ir/x/t/go-build4249258931/testprog.exe LockOSThreadMain (3.989747ms): ok
    proc_test.go:989: /home/swarming/.swarming/w/ir/x/t/go-build4249258931/testprog.exe LockOSThreadAlt: exit status 2
    proc_test.go:991: want "OK\n", got "panic: runtime error: index out of range [2] with length 0\n\ngoroutine 1 [running]:\nmain.tidExists(0xba?)\n\t/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/testdata/testprog/syscalls_linux.go:25 +0xdd\nmain.LockOSThreadAlt()\n\t/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/testdata/testprog/lockosthread.go:93 +0x185\nmain.main()\n\t/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/testdata/testprog/main.go:34 +0x133\n"
--- FAIL: TestLockOSThreadExit (0.02s)

— watchflakes

@mknyszek mknyszek self-assigned this Feb 28, 2024
@mknyszek mknyszek moved this to In Progress in Go Compiler / Runtime Feb 28, 2024
@gopherbot
Copy link
Contributor Author

Change https://go.dev/cl/567938 mentions this issue: runtime: be more defensive in tidExists about /proc/self/task/<tid>/stat

@github-project-automation github-project-automation bot moved this from In Progress to Done in Go Compiler / Runtime Mar 21, 2024
@golang golang locked and limited conversation to collaborators Mar 21, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@mknyszek mknyszek

Labels
compiler/runtime Issues related to the Go compiler and/or runtime. FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
Go Compiler / Runtime
Status: Done
Test Flakes
Archived in project
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mknyszek @gopherbot