From: Tom Tromey <tromey@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH 2/4] introduce parallel mode
Date: Thu, 18 Jul 2013 13:36:00 -0000 [thread overview]
Message-ID: <87txjsc7mw.fsf@fleche.redhat.com> (raw)
In-Reply-To: <51E7E27E.5030800@codesourcery.com> (Yao Qi's message of "Thu, 18 Jul 2013 20:41:34 +0800")
Tom> Second, this adds an "inotify" mode. If you have the inotifywait
Tom> command (part of inotify-tools), you can set the GDB_INOTIFY variable.
Tom> This will tell the test suite to watch for changes outside of the
Tom> allowed output directories.
Tom> This mode is useful for debugging the test suite, as it issues a
Tom> report whenever a possibly parallel-unsafe file open is done.
Yao> Where can I get this report? is it mixed in testsuite/gdb.log? An
Yao> example here would be helpful.
Good idea :)
It is just printed to the stdout of runtest. That's because we just
invoke inotifywait without redirections. I suppose if we have the file
descriptor of the log file available, we could send the output to the
log.
Here's a case where the test suite still makes a file outside the
allowed directories:
barimba. runtest GDB_INOTIFY=yes GDB_PARALLEL=yes --directory=gdb.server
[...]
Running ../../../archer/gdb/testsuite/gdb.server/ext-run.exp ...
Running ../../../archer/gdb/testsuite/gdb.server/file-transfer.exp ...
./ CREATE down-server
./ CREATE up-server
./ DELETE down-server
./ DELETE up-server
./ CREATE down-server
./ CREATE up-server
./ DELETE down-server
./ DELETE up-server
Running ../../../archer/gdb/testsuite/gdb.server/no-thread-db.exp ...
Running ../../../archer/gdb/testsuite/gdb.server/server-exec-info.exp ...
Tom
next prev parent reply other threads:[~2013-07-18 13:36 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 1/4] more uses of standard_output_file 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 [this message]
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
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-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=87txjsc7mw.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.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