This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH][gdb/testsuite] Don't expect gdb_prompt in mi_skip_python_test
- From: Tom de Vries <tdevries at suse dot de>
- To: Simon Marchi <simark at simark dot ca>, gdb-patches at sourceware dot org
- Date: Thu, 1 Aug 2019 14:41:33 +0200
- Subject: Re: [PATCH][gdb/testsuite] Don't expect gdb_prompt in mi_skip_python_test
- References: <20190727175221.GA9077@delia> <0389a280-4dc8-5e4c-fb4c-bc7c41f52afc@simark.ca> <c51e41a4-561d-cd65-ba6f-8e6df590a50f@suse.de>
On 29-07-19 11:33, Tom de Vries wrote:
>> It seems like this failure is reproducible using "make check-read1".
> It is indeed.
>
>> If you haven't
>> seen that before, check it out in gdb/testsuite/README,
> Thanks for the pointer. I've rewritten the rationale to use this concept
> rather than the trigger patch to reproduce the failure.
>
>> I'm sure you'll find dozens
>> of other testsuite bugs with it :).
> I did a testrun overnight, and yes, that's indeed the case :)
>
I've cleaned up all regular FAILs, and some timeout FAILs, and submitted
a patch for one more timeout FAIL (
https://sourceware.org/ml/gdb-patches/2019-08/msg00006.html ).
There are still 3 timeout FAILs left (see also PR24863 - Handle timeouts
with check-read1,
https://sourceware.org/bugzilla/show_bug.cgi?id=24863), and I've asked
for help from people who've edited those tests before.
Thanks,
- Tom