This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug go/52359] New: time test is too load-sensitive
- From: "ro at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 23 Feb 2012 17:35:16 +0000
- Subject: [Bug go/52359] New: time test is too load-sensitive
- Auto-submitted: auto-generated
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52359
Bug #: 52359
Summary: time test is too load-sensitive
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: go
AssignedTo: ian@airs.com
ReportedBy: ro@gcc.gnu.org
Host: i386-pc-solaris2.10
Target: i386-pc-solaris2.10
Build: i386-pc-solaris2.10
It seems that the libgo time test is too load-sensitive: I've seen it fail
several times like this:
--- FAIL: time_test.TestTicker (1.43 seconds)
???:1: 10 100ms ticks took 1.432394s, expected [800ms,1.2s]
FAIL
FAIL: time
--- FAIL: time_test.TestTicker (1.30 seconds)
???:1: 10 100ms ticks took 1.301332s, expected [800ms,1.2s]
FAIL
FAIL: time
This happens more often on a Sun Fire X4450 (4 x 2.93 GHz Xeon X7350), where
make check is run with -j<2 * ncore>.
Rainer