See https://groups.google.com/d/topic/golang-dev/tBtPnUcMkLw/discussion

Related to #13968. The failure below is fixed by setting ulimit -u higher, so this is a documentation/error reporting issue rather than one of behaviour.

1. What version of Go are you using (go version)?
   go1.6.2
2. What operating system and processor architecture are you using (go env)?
   GOARCH="amd64"
   GOBIN=""
   GOEXE=""
   GOHOSTARCH="amd64"
   GOHOSTOS="linux"
   GOOS="linux"
   GOPATH="/home/kortschak/Development"
   GORACE=""
   GOROOT="/home/kortschak/go"
   GOTOOLDIR="/home/kortschak/go/pkg/tool/linux_amd64"
   GO15VENDOREXPERIMENT="1"
   CC="gcc"
   GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0"
   CXX="g++"
   CGO_ENABLED="1"
3. What did you do?
   run all.bash.
4. What did you expect to see?
   Successful build and test.
5. What did you see instead?
   Test failure (excerpted):

##### ../test
# go run run.go -- bigalg.go
exit status 2
# command-line-arguments
runtime: failed to create new OS thread (have 6 already; errno=11)
fatal error: newosproc