https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84215
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84215
--- Comment #12 from Christophe Lyon ---
It's not very informative.
On arm:
PASS: crypto/x509
timed out in gotest
/home/tcwg-buildslave/workspace/tcwg-buildfarm/tcwg-apm_32-build/snapshots/gcc.git~master/libgo/testsuite/gotest:
line 624: 15642
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84215
--- Comment #11 from Ian Lance Taylor ---
Please include all the output from each failure, if possible. Thanks.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84215
--- Comment #10 from Christophe Lyon ---
Yesterday I noticed:
* on arm:
FAIL: libgo:database/sql
* on aarch64:
FAIL: libgo:runtime/pprof
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84215
--- Comment #9 from H.J. Lu ---
On i686 with many cores, r257758 gave:
...
goroutine 24690 [GC worker (idle)]:
runtime.mcall
/export/gnu/import/git/sources/gcc/libgo/runtime/proc.c:342
runtime.gopark
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84215
--- Comment #8 from Christophe Lyon ---
Still seeing at least os/signal having random pass/fail.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84215
--- Comment #7 from Ian Lance Taylor ---
I just committed a patch that may affect some of these failures. Please let me
know if you notice any change. Thanks.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84215
--- Comment #6 from ian at gcc dot gnu.org ---
Author: ian
Date: Mon Feb 12 18:50:16 2018
New Revision: 257599
URL: https://gcc.gnu.org/viewcvs?rev=257599=gcc=rev
Log:
PR go/84215
runtime, sync/atomic: use write barrier for atomic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84215
--- Comment #5 from Christophe Lyon ---
Today on ARM:
--- FAIL: TestExtraFiles (1.19s)
testing.go:560: TestExtraFiles: Something already leaked - closed fd 63
testing.go:560: Run: exit status 1; stdout "leaked parent file. fd =
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84215
H.J. Lu changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84215
--- Comment #3 from Christophe Lyon ---
> FAIL: context
> but the next build is still running, I don't know yet if it passes.
Next build completed, and:
PASS: context
Did something change wrt this test since yesterday?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84215
--- Comment #2 from Christophe Lyon ---
Well, we have a nightly Jenkins job that builds GCC (from scratch) and runs
'make check' on ARM, AArch64, and x86 hosts, and from time to time we see
regression reports on the mentioned tests.
And the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84215
--- Comment #1 from Ian Lance Taylor ---
What do you mean by "random results?" Can you post some output? Thanks.
13 matches
Mail list logo