Johan Corveleyn wrote on Sat, Feb 22, 2014 at 15:46:21 +0100:
> On Thu, Feb 13, 2014 at 7:30 AM, Ben Reser <b...@reser.org> wrote:
> > The 1.9.0-alpha1 release artifacts are now available for testing/signing.
> > Please get the tarballs from
> > https://dist.apache.org/repos/dist/dev/subversion
> > and add your signatures there. There's no particular schedule to this and I
> > wouldn't be surprised if we don't find some sort of problems in testing.
> >
> > Thanks!
>
> Another failure, when I test with FSX (over ra_local). The test run stops
> with:
>
> [[[
> ...
> [049/107]
> wc-test.exe...................................................success
> [050/107]
> window-test.exe...............................................success
> [051/107] changes-test.exeTraceback (most recent call last):
> File "win-tests.py", line 766, in <module>
> failed = th.run(tests_to_run)
> File
> "C:\research\svn\client_build\subversion-1.9.0-alpha1\build\run_tests.py",
> line 198, in run
> failed = self._run_test(prog, cnt, len(list)) or failed
> File
> "C:\research\svn\client_build\subversion-1.9.0-alpha1\build\run_tests.py",
> line 612, in _run_test
> os.chdir(progdir)
> WindowsError: [Error 2] The system cannot find the file specified:
> 'subversion/tests/libsvn_fs_base'
> ]]]
>
> I don't have changes-test.exe built. I don't compile with bdb, maybe
> that's the problem? So why is the test suite trying to run this test
> while I have no bdb enabled (assuming changes-test is bdb-specific)?
Does this get you farther?
Index: win-tests.py
===================================================================
--- win-tests.py (revision 1570855)
+++ win-tests.py (working copy)
@@ -257,8 +257,8 @@
if not fs_type:
fs_type = 'fsfs'
-# Don't run bdb tests if they want to test fsfs
-if fs_type == 'fsfs':
+# Don't run bdb tests if they want to test fsfs or fsx
+if fs_type != 'bdb':
all_tests = gen_obj.test_progs + gen_obj.scripts
if run_httpd:
> Also, a bit strange is that all other exe-tests are run in
> alphabetical order (window-test.exe being the last one), and then at
> 51 changes-test.exe shows up.
I think it's normal that BDB C tests follow the "core" C tests. (Look
at the prior initialization of ALL_TESTS)
