go: runtime: darwin memory corruption?
What is going on here?
https://storage.googleapis.com/go-build-log/5914916e/darwin-amd64-10_11_7e43df8a.log
ok internal/trace 0.572s
ok io 0.033s
ok io/ioutil 0.011s
ok log 0.009s
ok log/syslog 1.336s
ok math 0.009s
ok math/big 1.266s
ok math/bits 0.026s
ok math/cmplx 0.012s
ok math/rand 0.377s
ok mime 0.013s
ok mime/multipart 0.271s
ok mime/quotedprintable 0.101s
ok net 8.465s
# net/http
/var/folders/dx/k53rs1s93538b4x20g46cj_w0000gn/T/workdir/go/src/net/http/request.go:535:23: bufio.size·3 declared and not used
FAIL net/http [build failed]
2017/12/04 12:10:04 Failed: exit status 2
Error: tests failed: dist test failed: go_test:net/http: exit status 1
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 23 (21 by maintainers)
Commits related to this issue
- runtime: mark heapBits.bits nosplit heapBits.bits is used during bulkBarrierPreWrite via heapBits.isPointer, which means it must not be preempted. If it is preempted, several bad things can happen: ... — committed to golang/go by aclements 7 years ago
- runtime: reset write barrier buffer on all flush paths Currently, wbBufFlush does nothing if the goroutine is dying on the assumption that the system is crashing anyway and running the write barrier ... — committed to golang/go by aclements 7 years ago
@mdempsky, they’re identical (same VM images). Only difference is trybot runs shard out over 4 VMs and build.golang.org runs shard out over 3 VMs.