Re: [PATCH] testsuite: disable break-interp.exp for Arm buildbot

[Alan Hayward <Alan.Hayward@arm.com>]

> On 9 Aug 2019, at 18:22, Pedro Alves <palves@redhat.com> wrote:
> 
> On 8/9/19 10:21 AM, Alan Hayward wrote:
> 
>> Use this test to disable gdb.base/break-interp.exp, 
> 
> I'd rather avoid completely skipping silently, since this way 
> nobody will ever remember to enable it back.
> 
>> as this test currently generates 132 sequential timeouts.
> 
> So, in the general case, when something like that happens, it's better
> to make the testcase bail out earlier in response to one of the
> failures.  Like, if we fail to run to a breakpoint or something, then
> there's no point in continuing the parts of the testcase that depend
> on running to that breakpoint.
> 
> Is there some fundamental failures in each of the iterations of
> the test that we could detect to skip most of the tests in each of
> the iterations?
> 
> From your mention of "fix stop on solib" not working, it sounds like the
> trouble is that when the testcase does "set stop-on-solib-events 1 + run",
> the inferior never stops and we time out.  Can you make reach_1 detect it
> and bail out without waiting for a time out?  Like, make the testcase
> put a breakpoint somewhere in case stop-on-solib-events fails to stop
> the inferior.
> 
> That'd be better since it'd record the FAILs, and it would be target
> independent.
> 

Agreed. It’s not quite that simple - the failures happen in cases where there
is no debug (eg BINprelinkNOdebugNOpieNO), so there is nowhere I can place
a breakpoint.

Maybe exit the test case if one of them times out?  (I’m not keen on that either).


Alan.