larsxschneider@xxxxxxxxx wrote: > Enable t9113 and 9126 by defining the SVNSERVER_PORT. Since both tests > open the same port during execution, they cannot run in parallel. Add > a ".seq.sh" suffix to the test files and teach "prove" to run them > sequentially. Interesting, I guess I forgot the problem because had some rules in config.mak to serialize them for many years, now :x Anyways, how about making the tests run on separate ports and not worry about serializing them at all? Maybe there was a reason we didn't do this years ago, but I forget... But probably the best (but I guess more difficult) option is to get svnserve+apache to do socket activation off a random port bound by a parent process at startup. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html