Branko Čibej wrote on Tue, 24 Nov 2020 18:44 +00:00: > On 24.11.2020 19:05, Alan Fry wrote: > > Having some time finally to work on building SVN (thanks all who > > helped me get this far), I setup a VM with Ubuntu. (Also setup a > > Windows 10 machine w/ Visual studio, but have not started on that > > effort yet). > > > > Knowing little about linux, I managed to get this far, the results of > > make checks > > > > Last part of the make check: > > > > At least one test FAILED, checking > > /home/svn/Documents/subversion-1.14.0/tests.log > > FAIL: error-test 3: test svn_error_symbolic_name > > FAIL: locks-test 14: lock/unlock when 'write-lock' couldn't be obtained > > FAIL: commit_tests.py 48: set revision props during remote property edit > > FAIL: prop_tests.py 1: write/read props in wc only (ps, pl, pdel, pe) > > FAIL: prop_tests.py 16: property operations on a URL > > FAIL: update_tests.py 38: update --accept automatic conflict resolution > > Summary of test results: > > 2508 tests PASSED > > 162 tests SKIPPED > > 81 tests XFAILED (17 WORK-IN-PROGRESS) > > 6 tests FAILED > > Python version: 3.8.5. > > SUMMARY: Some tests failed > > > > Are these errors something I need to dig into, indicating that my > > build is no good? I was reading in the "INSTALL" document, there is > > mention that some errors are expected. Is there a way to determine if > > these are expected errors? > > Expected test failures are tagged as XFAIL, not FAIL. So these are > "real" failures. Also the summary line would read "All tests succeeded" > if there were only expected failures. > > You should look at tests.log (the test driver hepfully prints the whole > path) to see why those tests failed, it could be something trivial. It's > not likely that there's a problem with the code, we'd have noticed that.
Since the test harness existed successfully, you can also look in fails.log, which is created next to tests.log at the end of a test run, and contains only "real" failures. Cheers, Daniel
