This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFA/testsuite] Remove all remaining gdb_suppress_entire_file


> Most of these are checking compile failures.  Are we still seeing some
> sort of ERROR about that in the testsuite output, or just UNTESTED?

The worst case I've had in the past was timeouts, it's been a while
though. But the reason I thought it was a good idea was that it didn't
seem to make sense to me to run the testcase anyway if we didn't manage
to build the test executable, did it. In other words, why announce that
all following tests will fail and run them nonetheless? It's not the
only reason because I wouldn't mind if that was just the case. But I
remember telling myself that I could have avoided a lot of grief at
certain times if we stopped the testcase after failing to do the compile.
The failures these tests detect put the testcase into a sort of degraded
mode, and dejagnu is not so good sometimes in these modes...

Sorry that my memory is so vague. Perhaps Daniel has more concrete
examples in mind...

-- 
Joel


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]