This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
[PATCH 00/13] test suite parallel safety
- From: Tom Tromey <tromey at redhat dot com>
- To: gdb-patches at sourceware dot org
- Date: Fri, 23 Aug 2013 14:36:37 -0600
- Subject: [PATCH 00/13] test suite parallel safety
This is the final series to make the test suite parallel-safe. As a
reminder, here parallel safety just means that a given test will not
write (or delete) files outside of the subdirectory assigned by the
gdb test harness.
Even after this series there are stragglers:
First, I only seriously tried this on a single architecture. So,
there are bound to be issues for other arches. These are generally
easy to fix; and, if you have inotifytools easy to diagnose as well.
I'll work on this as time permits. I think this is less serious than
it may sound, as there aren't really that many arch-specific tests
that are likely to have clashes.
Second, Fortran:
Running ../../../archer/gdb/testsuite/gdb.fortran/library-module.exp ...
./ CREATE lib.mod0
./ DELETE lib.mod0
./ CREATE libmany.mod0
./ DELETE libmany.mod0
Running ../../../archer/gdb/testsuite/gdb.fortran/module.exp ...
./ CREATE mod1.mod0
./ DELETE mod1.mod0
./ CREATE mod2.mod0
./ DELETE mod2.mod0
./ CREATE modmany.mod0
./ DELETE modmany.mod0
./ CREATE moduse.mod0
./ DELETE moduse.mod0
This happens because the compiler generates these files. I don't know
of a good, portable (across Fortran compilers) way to fix this.
This is only an issue in practice if we have multiple Fortran modules
with the same name.
And, finally:
Running ../../../archer/gdb/testsuite/gdb.trace/save-trace.exp ...
./ CREATE savetrace.tr
./ DELETE savetrace.tr
This is a test for a directory-less save. It seemed wrong to change
it.
I regression tested this series on x86-64 Fedora 18, both with
GDB_PARALLEL set and without.
After this series, I think we're ready to enable the new parallel
code.
Tom