testsanitizers fails for all.bash run

[Danny]

Hi all,

I've had this particular test fail for a few different revisions now, so I thought I should send a message, to be sure it's on the radar. I didn't find any thread on this topic on groups.google.com. All existing threads seemed to be outdated.

This happens repeatedly on a (very basic) HP notebook with Intel(R) Celeron(R) CPU  N3050  @ 1.60GHz (dual-core IIRC). The OS is 64-bit Debian Testing, fully updated as of time of writing. Since this is not exactly a very powerful notebook, I let it run without doing anything else. This is a fresh install, only a few days old, so this could be caused by a missing dependency.

The Go sources are cloned from go.googlesource.com/go and bootstrapped with Go-1.4, again from go.googlesource.com, release-branch.

Does anyone know what this is about? Is there anything I need to do? Let me know if there is any additional information needed!

Danny


% go env
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/danny/Apps/golang/env"
GORACE=""
GOROOT="/home/danny/Apps/golang/go"
GOTOOLDIR="/home/danny/Apps/golang/go/pkg/tool/linux_amd64"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build326308358=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"


~/Apps/golang/go/src % GOROOT_BOOTSTRAP=~/Apps/golang/go-1.4 ./all.bash
...
##### ../misc/cgo/testasan

##### ../misc/cgo/testsanitizers
skipping msan tests: -fsanitize=memory not supported
==================
WARNING: ThreadSanitizer: data race (pid=22805)
  Write of size 4 at 0x0000006ae1b8 by thread T2:
    #0 setVal /home/danny/Apps/golang/go/misc/cgo/testsanitizers/tsan.go:22 (tsan+0x0000004453b0)
    #1 _cgo_82605fb7dc7c_Cfunc_setVal /home/danny/Apps/golang/go/misc/cgo/testsanitizers/tsan.go:96 (tsan+0x000000445431)
    #2 runtime.asmcgocall <null> (tsan+0x0000004426df)

  Previous write of size 4 at 0x0000006ae1b8 by main thread:
    #0 setVal /home/danny/Apps/golang/go/misc/cgo/testsanitizers/tsan.go:22 (tsan+0x0000004453b0)
    #1 _cgo_82605fb7dc7c_Cfunc_setVal /home/danny/Apps/golang/go/misc/cgo/testsanitizers/tsan.go:96 (tsan+0x000000445431)
    #2 runtime.asmcgocall <null> (tsan+0x0000004426df)

  Location is global 'val' of size 4 at 0x0000006ae1b8 (tsan+0x0000006ae1b8)

  Thread T2 (tid=22814, running) created by main thread at:
    #0 pthread_create <null> (libtsan.so.0+0x000000026e64)
    #1 _cgo_sys_thread_start /home/danny/Apps/golang/go/src/runtime/cgo/gcc_linux_amd64.c:73 (tsan+0x00000044573e)

SUMMARY: ThreadSanitizer: data race /home/danny/Apps/golang/go/misc/cgo/testsanitizers/tsan.go:22 setVal
==================
FAIL: tsan
==================
WARNING: ThreadSanitizer: data race (pid=22912)
  Write of size 4 at 0x0000006ae108 by thread T2:
    #0 setVal /home/danny/Apps/golang/go/misc/cgo/testsanitizers/tsan2.go:32 (tsan2+0x000000445490)
    #1 _cgo_b3c556dc7343_Cfunc_setVal /home/danny/Apps/golang/go/misc/cgo/testsanitizers/tsan2.go:106 (tsan2+0x000000445601)
    #2 runtime.asmcgocall <null> (tsan2+0x0000004427ef)

  Previous write of size 4 at 0x0000006ae108 by main thread:
    #0 run /home/danny/Apps/golang/go/misc/cgo/testsanitizers/tsan2.go:24 (tsan2+0x0000004454f9)
    #1 _cgo_b3c556dc7343_Cfunc_run /home/danny/Apps/golang/go/misc/cgo/testsanitizers/tsan2.go:92 (tsan2+0x0000004455ad)
    #2 runtime.asmcgocall <null> (tsan2+0x0000004427ef)

  Location is global 'val' of size 4 at 0x0000006ae108 (tsan2+0x0000006ae108)

  Thread T2 (tid=22916, running) created by main thread at:
    #0 pthread_create <null> (libtsan.so.0+0x000000026e64)
    #1 _cgo_sys_thread_start /home/danny/Apps/golang/go/src/runtime/cgo/gcc_linux_amd64.c:73 (tsan2+0x00000044590e)

SUMMARY: ThreadSanitizer: data race /home/danny/Apps/golang/go/misc/cgo/testsanitizers/tsan2.go:32 setVal
==================
FAIL: tsan2
2016/04/12 22:48:59 Failed: exit status 1

[Ian Lance Taylor]

On Tue, Apr 12, 2016 at 2:51 PM, Danny <danny.v...@gmail.com> wrote:
>
> I've had this particular test fail for a few different revisions now, so I
> thought I should send a message, to be sure it's on the radar. I didn't find
> any thread on this topic on groups.google.com. All existing threads seemed
> to be outdated.

This is https://golang.org/issue/14602 .

Ian