This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Go patch committed: New lock/note implementation
- From: Ian Lance Taylor <iant at google dot com>
- To: Rainer Orth <ro at CeBiTec dot Uni-Bielefeld dot DE>
- Cc: gcc-patches at gcc dot gnu dot org, gofrontend-dev at googlegroups dot com
- Date: Thu, 01 Dec 2011 15:40:15 -0800
- Subject: Re: Go patch committed: New lock/note implementation
- References: <mcr62ibdhwi.fsf@dhcp-172-18-216-180.mtv.corp.google.com> <yddty5sjfgz.fsf@manam.CeBiTec.Uni-Bielefeld.DE> <yddobw0xch2.fsf@manam.CeBiTec.Uni-Bielefeld.DE> <mcrwraivbdv.fsf@dhcp-172-18-216-180.mtv.corp.google.com> <ydd39d4tf0u.fsf@manam.CeBiTec.Uni-Bielefeld.DE>
Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> writes:
> FAIL: go.go-torture/execute/go-1.go execution, -O0
There should be more information in gcc/testsuite/go/go.log.
> * All 64-bit libgo tests fail on the same target:
>
> FAIL: asn1
> /vol/gcc/src/hg/trunk/local/libgo/testsuite/gotest[422]: gotest-timeout: cannot create [No such file or directory]
> checkId: 65 should be 1
> checkId: 66 should be 1
>
> I've not yet investigated what's going on here.
I don't know what is going on either.
gotest-timeout is just a file created by the gotest script:
(sleep `expr $timeout + 10`
echo > gotest-timeout
echo "timed out in gotest" 1>&2
kill -9 $pid) &
The error above implies that gotest is running in a directory which was
removed while the script was running. I don't really see how libgo
could cause that to happen. Could something else have been going on?
At this point I have no idea what is going wrong.
Ian