I currently get the following output from the named_atomic tests, running on the same box as the build slave:
$ ./named_atomic-test subversion/tests/libsvn_subr/named_atomic-test.c:336: (apr_err=200029) subversion/tests/libsvn_subr/named_atomic-test.c:59: (apr_err=200029) subversion/libsvn_subr/svn_named_atomic.c:396: (apr_err=200029) subversion/libsvn_subr/svn_named_atomic.c:304: (apr_err=200029) subversion/libsvn_subr/atomic.c:60: (apr_err=200029) svn_tests: E200029: Couldn't perform atomic initialization subversion/libsvn_subr/io.c:3098: (apr_err=13) svn_tests: E000013: Can't open file '/tmp/SvnAtomicsMutex': Permission denied FAIL: lt-named_atomic-test 1: basic r/w access to a single atomic ... [ More of the same. ] $ whoami hwright $ ls -l /tmp total 4 -rw------- 1 buildbot nogroup 0 Apr 15 06:27 SvnAtomicsMutex -rw------- 1 buildbot nogroup 8 Apr 15 07:14 SvnTestsShm $ It appears that the buildslave created the two above files in the tmp directory, so when I attempt to run a completely independent set of tests, they run into those existing files and throw and error. The suggestion was made on IRC to set the temp directory for the buildslave to somewhere else, but that doesn't solve the problem, just masks it. Anybody running separate svn processes on the same box would run into the same problem, which makes this a bona fide error condition. Whoever caused these failures, please look into fixing them. Thanks, -Hyrum -- uberSVN: Apache Subversion Made Easy http://www.uberSVN.com/
