-
Notifications
You must be signed in to change notification settings - Fork 18k
database/sql: race detector is not happy on darwin/amd64 #6928
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.
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
Labels
Milestone
Comments
Looks like it's not just darwin/amd64-race, http://build.golang.org/log/3a3621414b48cdc38a65ca1bfd5afd513dbf71d7 Labels changed: removed os-macosx. |
I was lucky enough to find sql.test wedged during a race build and hit it with SIGQUIT PASS BenchmarkConcurrentDBExec-4 5 37539173 ns/op 2354108 B/op 14705 allocs/op BenchmarkConcurrentStmtQuery-4 5 33826012 ns/op 2754566 B/op 18224 allocs/op BenchmarkConcurrentStmtExec-4 5 25281842 ns/op 1922510 B/op 4179 allocs/op BenchmarkConcurrentTxQuery-4 SIGQUIT: quit PC=0x2912b runtime.mach_semaphore_wait() /Users/builder/workspace/darwin-amd64-race-cheney-36d5461843ce/go/src/pkg/runtime/sys_darwin_amd64.s:395 +0xb runtime.semasleep(0xffffffffffffffff) /Users/builder/workspace/darwin-amd64-race-cheney-36d5461843ce/go/src/pkg/runtime/os_darwin.c:414 +0xa1 runtime.notesleep(0x489328) /Users/builder/workspace/darwin-amd64-race-cheney-36d5461843ce/go/src/pkg/runtime/lock_sema.c:164 +0xc9 stopm() /Users/builder/workspace/darwin-amd64-race-cheney-36d5461843ce/go/src/pkg/runtime/proc.c:932 +0xe1 gcstopm() /Users/builder/workspace/darwin-amd64-race-cheney-36d5461843ce/go/src/pkg/runtime/proc.c:1100 +0xc5 schedule() /Users/builder/workspace/darwin-amd64-race-cheney-36d5461843ce/go/src/pkg/runtime/proc.c:1296 +0x4a goexit0(0xc21004fea0) /Users/builder/workspace/darwin-amd64-race-cheney-36d5461843ce/go/src/pkg/runtime/proc.c:1417 +0x102 runtime.mcall(0x26d9d) /Users/builder/workspace/darwin-amd64-race-cheney-36d5461843ce/go/src/pkg/runtime/asm_amd64.s:178 +0x4b goroutine 1 [chan receive]: testing.(*B).run(0xc2100513c0, 0x3, 0x5cdd60, 0x1, 0x1, ...) /Users/builder/workspace/darwin-amd64-race-cheney-36d5461843ce/go/src/pkg/testing/benchmark.go:171 +0x6c testing.RunBenchmarks(0x26d4c8, 0x47a960, 0x8, 0x8) /Users/builder/workspace/darwin-amd64-race-cheney-36d5461843ce/go/src/pkg/testing/benchmark.go:303 +0x6bb testing.Main(0x26d4c8, 0x47d1a0, 0x29, 0x29, 0x47a960, ...) /Users/builder/workspace/darwin-amd64-race-cheney-36d5461843ce/go/src/pkg/testing/testing.go:411 +0x217 main.main() /tmp/builder/go-build150197137/database/sql/_test/_testmain.go:143 +0xdd goroutine 67 [chan receive]: database/sql.(*DB).connectionOpener(0xc210053680) /Users/builder/workspace/darwin-amd64-race-cheney-36d5461843ce/go/src/pkg/database/sql/sql.go:574 +0x5f created by database/sql.Open /Users/builder/workspace/darwin-amd64-race-cheney-36d5461843ce/go/src/pkg/database/sql/sql.go:436 +0x348 goroutine 60 [running]: goroutine running on other thread; stack unavailable created by testing.(*B).run /Users/builder/workspace/darwin-amd64-race-cheney-36d5461843ce/go/src/pkg/testing/benchmark.go:170 +0x3c rax 0xe rbx 0x489328 rcx 0x7fff5fbffb08 rdx 0xffffffffffffffff rdi 0x1503 rsi 0x0 rbp 0x4845c0 rsp 0x7fff5fbffb08 r8 0x41 r9 0xa9 r10 0x5b9000 r11 0x286 r12 0x0 r13 0x1726d18366f48 r14 0x134641dc2d5c2200 r15 0x0 rip 0x2912b rflags 0x286 cs 0x7 fs 0x20000000 gs 0x80000 exit status 2 FAIL database/sql 155.329s I need to collect more samples, but it looks to me like stop-the-world has been declared, but another g is spinning preventing the gc from running. |
Looks related to: https://golang.org/issue/7008&q=owner%3Acshapiro%40golang.org&colspec=ID%20Status%20Stars%20Release%20Owner%20Repo%20Summary Owner changed to @lexprfuncall. |
Owner changed to @dvyukov. |
Issue #7008 has been merged into this issue. |
Russ, can you take a look at this? I think it's also liveness issues. Owner changed to @rsc. |
This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The text was updated successfully, but these errors were encountered: