Re: [PATCH 2/4] introduce parallel mode

[Tom Tromey <tromey at redhat dot com>]

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