From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2] Improve analysis of racy testcases
Date: Sun, 06 Mar 2016 01:44:00 -0000 [thread overview]
Message-ID: <87ziucv0qf.fsf@redhat.com> (raw)
In-Reply-To: <56D58E00.2030503@redhat.com> (Pedro Alves's message of "Tue, 1 Mar 2016 12:41:36 +0000")
On Tuesday, March 01 2016, Pedro Alves wrote:
> On 03/01/2016 05:51 AM, Sergio Durigan Junior wrote:
>
>> # Note that we must resort to a recursive make invocation here,
>> @@ -190,6 +197,26 @@ DO_RUNTEST = \
>> check-single:
>> $(DO_RUNTEST) $(RUNTESTFLAGS) $(expanded_tests_or_none)
>>
>> +check-single-racy:
>
> (...)
>
>> + $(srcdir)/analyze-racy-logs.py \
>> + `ls racy_outputs/gdb*.sum` > racy.sum; \
>
> This ls invocation needs updating.
Fixed.
>> + sed -n '/=== gdb Summary ===/,$$ p' racy.sum
>> +
>
>
>> diff --git a/gdb/testsuite/README b/gdb/testsuite/README
>> index 6b59027..043a8bd 100644
>> --- a/gdb/testsuite/README
>> +++ b/gdb/testsuite/README
>> @@ -50,6 +50,51 @@ to any non-empty value:
>> If you want to use runtest directly instead of using the Makefile, see
>> the description of GDB_PARALLEL below.
>>
>> +Racy testcases
>> +**************
>> +
>> +Sometimes, new testcases are added to the testsuite that are not
>> +entirely deterministic, and can randomly pass or fail. We call them
>> +"racy testcases", and they can be bothersome when one is comparing
>> +different testsuite runs. In order to help identifying them, it is
>> +possible to run the tests several times in a row and ask the testsuite
>> +machinery to analyze the results. To do that, you need to specify the
>> +RACY_ITER environment variable to make:
>
> Nicer, thanks. :-)
>
>
>> +
>> + # Print the header.
>> + print "\t\t=== gdb tests ===\n"
>
> "gdb racy tests" ?
Fixed.
>> +
>> + # Print each test.
>> + for line in sorted (racy_tests):
>> + print line
>> +
>> + # Print the summary.
>> + print "\n"
>> + print "\t\t=== gdb Summary ===\n"
>> + print "# of racy testcases:\t\t%d" % len (racy_tests)
>
> AFAICS, it's # of racy tests, not # of racy testcases, right?
Yeah, fixed.
> Feel free to push with the above addressed.
Thanks, pushed.
fb6a751f5f1fe7912e84dd90d06395c357da47c2
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2016-03-06 1:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87r3gcgm91.fsf@redhat.com>
2016-02-25 17:01 ` [PATCH] " Pedro Alves
2016-02-28 21:44 ` Sergio Durigan Junior
2016-03-01 11:56 ` Pedro Alves
2016-03-06 1:29 ` Sergio Durigan Junior
2016-02-25 18:34 ` Antoine Tremblay
2016-03-01 5:58 ` Sergio Durigan Junior
2016-03-14 12:32 ` Antoine Tremblay
2016-03-14 12:45 ` Pedro Alves
2016-03-14 14:04 ` Antoine Tremblay
2016-04-27 17:18 ` Antoine Tremblay
2016-03-01 5:51 ` [PATCH v2] " Sergio Durigan Junior
2016-03-01 12:41 ` Pedro Alves
2016-03-06 1:44 ` Sergio Durigan Junior [this message]
2016-03-06 22:34 ` [commit/obvious] Set executable bit on analyze-racy-logs.py Sergio Durigan Junior
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=87ziucv0qf.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
/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