From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: Doug Evans <dje@google.com>,
Joel Brobecker <brobecker@adacore.com>,
Simon Marchi <simon.marchi@ericsson.com>,
gdb-patches <gdb-patches@sourceware.org>,
Yao Qi <qiyaoltc@gmail.com>
Subject: Re: [PATCH] Remove symlinks created in argv0-symlink.exp and general cleanup
Date: Wed, 12 Aug 2015 16:40:00 -0000 [thread overview]
Message-ID: <87r3n85ukx.fsf@redhat.com> (raw)
In-Reply-To: <55CB123F.70603@redhat.com> (Pedro Alves's message of "Wed, 12 Aug 2015 10:30:39 +0100")
On Wednesday, August 12 2015, Pedro Alves wrote:
>> As for whether to always have one directory per test
>> (in serial and parallel modes), that *could* be treated as a separate
>> issue, but if it reduces complexity by doing the same thing
>> for serial and parallel then great.
>
> I believe this would be worthwhile.
>
> Taking this a step further, if we always ran in parallel mode (the
> equivalent of make check -j1 FORCE_PARALLEL=1), then variable bleeding
> between tests would no longer be an issue, as then we'd invoke a
> dejagnu/runtest per test. That would mean making GNU Make a
> requirement for testing (which IMO, should be OK).
FWIW, this would be awesome. I am not sure about forcing the dependency
on GNU Make for the testing (this would be OK by me, but maybe someone
has a case against), but defaulting to FORCE_PARALLEL=1 would be a step
forward, indeed. While hacking our testsuite to implement a way to
verify the racy tests we have, I could see how the fact that each test
has its own directory makes a difference.
Thanks,
--
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:[~2015-08-12 16:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 20:13 Simon Marchi
2015-08-03 14:23 ` Pedro Alves
2015-08-03 15:16 ` Simon Marchi
2015-08-03 16:34 ` Pedro Alves
2015-08-03 16:38 ` Pedro Alves
2015-08-03 18:10 ` Simon Marchi
2015-08-03 18:42 ` Pedro Alves
2015-08-04 16:11 ` Sergio Durigan Junior
2015-08-04 17:21 ` Joel Brobecker
2015-08-11 17:36 ` Doug Evans
2015-08-11 19:58 ` Joel Brobecker
2015-08-11 20:43 ` Doug Evans
2015-08-11 23:02 ` Joel Brobecker
2015-08-12 9:30 ` Pedro Alves
2015-08-12 16:40 ` Sergio Durigan Junior [this message]
2015-08-12 17:22 ` Joel Brobecker
2015-08-12 17:38 ` Doug Evans
2015-08-12 18:43 ` Joel Brobecker
2015-08-12 18:50 ` Doug Evans
2015-08-12 19:41 ` Joel Brobecker
2015-08-12 20:23 ` Doug Evans
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=87r3n85ukx.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=brobecker@adacore.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=qiyaoltc@gmail.com \
--cc=simon.marchi@ericsson.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