I won't give my test user full root rights :-)
And yes in the MySQL case this might be possible to use different tables
but this can be more compilcated with other resources being used (shared
memory? pop3-daemons for ext/imap tests, etc.) But I'd prefer some
simple locking mechanism ...
The code is currently set up to run groups (directories) of tests in parallel, not individual test cases. It is currently assumed that all tests in a group (directory) will be run in sequence. The experiments I did earlier showed that this works well.
A simple mechanism which might help us work around not being able to run say, different types of database test at the same time, is is to use a "group configuration file". At the moment there is a 'run configuration' and a 'test configuration', the 'test configuration' specifies settings that are for a single test (for example if the test has an --INI-- section).
If we introduce a 'group configuration' it could specify, for example:
"the tests in this directory cannot be run at the same time as those in XYZ directory"
"the tests in this directory cannot be run at the same time as ANY other tests"
....
This would be reasonably easy to implement by adding an extra configuration file to every directory which contains .phpt files, or at least those that cannot be run at the same time as other tests. No other changes to existing tests would be needed (...and having spent a couple of hours this morning fixing up broken tests this seems like a big plus to me :-) )
Zoe