Didier Spezia dc5315c341 build: prevent the entire repo to be wiped out by cgo test scripts ... Following the parallelization of some tests, a race condition can occur in testcarchive, testshared and testcshared. In some cases, it can result in the go env GOROOT command returning corrupted data, which are then passed to a rm command. Make the shell script more robust by not trusting the result of the go env GOROOT command. It does not really fix the issue, but at least prevent the entire repository to be deleted. Updates #13789 Change-Id: Iaf04a7bd078ed3a82e724e35c4b86e6f756f2a2f Reviewed-on: https://go-review.googlesource.com/18173 TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Russ Cox <rsc@golang.org>		2016-01-04 19:56:30 +00:00
..
src	runtime: for c-archive/c-shared, don't install unnecessary signal handlers	2015-12-18 22:27:38 +00:00
main0.c	cmd/go: install headers for c-archive/c-shared cgo exports	2015-05-07 17:39:56 +00:00
main1.c	misc/cgo/testcshared: test -buildmode=c-shared	2015-04-17 16:16:44 +00:00
main2.c	misc/cgo/testcshared: use fd 100 instead of fd 10 for back-channel communication	2015-12-05 03:56:23 +00:00
main3.c	misc/cgo/testcshared: add a c-shared test for android/arm.	2015-04-24 16:32:31 +00:00
main4.c	runtime: for c-archive/c-shared, don't install unnecessary signal handlers	2015-12-18 22:27:38 +00:00
test.bash	build: prevent the entire repo to be wiped out by cgo test scripts	2016-01-04 19:56:30 +00:00