From: Antoine Tremblay <antoine.tremblay@ericsson.com>
To: Antoine Tremblay <antoine.tremblay@ericsson.com>
Cc: Sergio Durigan Junior <sergiodj@redhat.com>,
GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Improve analysis of racy testcases
Date: Wed, 27 Apr 2016 17:18:00 -0000 [thread overview]
Message-ID: <wwok60v30y3f.fsf@ericsson.com> (raw)
In-Reply-To: <wwokk2l51bra.fsf@ericsson.com>
Antoine Tremblay writes:
>> As for the exclusion list you mentioned, DejaGNU's runtest allows one to
>> specify a --ignore flag with the names of the tests you don't want to
>> run. It should be possible to pass this via RUNTESTFLAGS, but I haven't
>> tried. I'll give it a go tomorrow.
>
> Great, I did not know that, I'll give it a try and that works no need to
> output the non-racy tests...
Just FYI, I just had a chance to try this and it works except you need
to forgo the path of the test so for example to ignore
gdb.trace/actions-changed.exp
You need : RUNTESTFLAGS='--ignore actions-changed.exp'
Not sure what happens if 2 tests have the same name buf a different directory..
Regards,
Antoine
next prev parent reply other threads:[~2016-04-27 17:18 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 ` 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 [this message]
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
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=wwok60v30y3f.fsf@ericsson.com \
--to=antoine.tremblay@ericsson.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@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