This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC-3.2.3 prerelease, 1st iteration
On Tue, Apr 15, 2003 at 05:23:54AM -0500, Loren James Rittle wrote:
> In article <200304151157 dot 55166 dot ebotcazou at libertysurf dot fr> you write:
>
> > I think you didn't split correctly, it's
>
> > WARNING: program timed out.
> > FAIL: thread/pthread4.cc execution test
>
> > I have seen this "problem" since I started testing on Sparc boxes (Ultra-2
> > and Ultra-60).
>
> Yes, as the author/installer of the test: It is probably harmless if
> the test fails with the "program timed out" message before the FAIL.
> It would be useful to check to see if it is "live/deadlocking", or
> really just not completing all iterations within the dejagnu time limit.
I use
set_board_info gcc,timeout 1200
set_board_info sim,timeout 1200
in /usr/share/dejagnu/baseboards/unix.exp to fix timeouts in the gcc
testsuite but I don't know how to set any such variable to get the
libstdc++-v3 testsuite use different time-out value than the 300
default one.. any one?
Cheers,
/ChJ