From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/4] introduce parallel mode
Date: Thu, 01 Aug 2013 16:56:00 -0000 [thread overview]
Message-ID: <51FA9350.2060808@redhat.com> (raw)
In-Reply-To: <1374073124-23602-3-git-send-email-tromey@redhat.com>
On 07/17/2013 03:58 PM, Tom Tromey wrote:
> First, it checks for the GDB_PARALLEL variable. If this is set (say,
> on the runtest command line), then the test suite assumes "parallel
> mode". In this mode, files are put into a subdirectory named after
> the test. That is, for DIR/TEST.exp, the outputs are put into
> ./outputs/DIR/TEST/.
>
> Second, this adds an "inotify" mode. If you have the inotifywait
> command (part of inotify-tools), you can set the GDB_INOTIFY variable.
> This will tell the test suite to watch for changes outside of the
> allowed output directories.
I think these variables should be documented in the internals
manual, in the "Testsuite Parameters" section.
--
Pedro Alves
next prev parent reply other threads:[~2013-08-01 16:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 14:58 [PATCH 0/4] introduce test suite "parallel" mode Tom Tromey
2013-07-17 14:59 ` [PATCH 4/4] add caching procs to test suite Tom Tromey
2013-08-01 17:10 ` Pedro Alves
2013-08-01 17:58 ` Tom Tromey
2013-07-17 14:59 ` [PATCH 3/4] add standard_temp_file Tom Tromey
2013-07-17 14:59 ` [PATCH 2/4] introduce parallel mode Tom Tromey
2013-07-18 12:42 ` Yao Qi
2013-07-18 13:36 ` Tom Tromey
2013-07-18 22:22 ` Yao Qi
2013-08-01 19:45 ` Tom Tromey
2013-08-01 20:58 ` Tom Tromey
2013-08-02 6:23 ` Yao Qi
2013-08-02 8:41 ` Pedro Alves
2013-08-02 15:02 ` Tom Tromey
2013-08-01 16:56 ` Pedro Alves [this message]
2013-07-17 14:59 ` [PATCH 1/4] more uses of standard_output_file Tom Tromey
2013-08-01 17:14 ` [PATCH 0/4] introduce test suite "parallel" mode Pedro Alves
2013-08-01 19:22 ` Tom Tromey
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=51FA9350.2060808@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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