Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Simon Marchi <simark@simark.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH][gdb/testsuite] Don't expect gdb_prompt in mi_skip_python_test
Date: Thu, 01 Aug 2019 12:41:00 -0000	[thread overview]
Message-ID: <4c28ded8-756b-7a04-a72f-37f8bc5cb182@suse.de> (raw)
In-Reply-To: <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


  reply	other threads:[~2019-08-01 12:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-27 17:52 Tom de Vries
2019-07-27 21:05 ` Kevin Buettner
2019-07-28  3:18 ` Simon Marchi
2019-07-29  9:33   ` Tom de Vries
2019-08-01 12:41     ` Tom de Vries [this message]
2019-08-01 14:02       ` Simon Marchi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4c28ded8-756b-7a04-a72f-37f8bc5cb182@suse.de \
    --to=tdevries@suse.de \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox