This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug other/18961] Large output causes testsuite failure
- From: "chris at bubblescope dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 13 Dec 2004 17:56:19 -0000
- Subject: [Bug other/18961] Large output causes testsuite failure
- References: <20041213171434.18961.chris@bubblescope.net>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From chris at bubblescope dot net 2004-12-13 17:56 -------
I'm fairly sure it's not a timeout (It takes <5 seconds to run on my computer).
It might be a dejagnu bug. Unfortunatly I find it very hard to find out exactly
what is causing this bug.
While I agree that allowing program's output to run out of control is a bad
idea, the problem with the current cutoff system is that it seems quite
unreliable. Around the mark at which the bug occurs (round about 200,000-300,000
characters on my computer) the test will sometimes run and sometimes fail. This
kind of unpredictable behaviour led me to a merry afternoon of debugging (I was
writing a test which outputed a large quantity of state information for testing
reasons) as it randomly appeared and disappeared. I do think that the behaviour
could be more reliable, and at least better documented.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18961