Thanks for the tests.log! I've tried to look into it and sending some comments below!
Den fre 31 mars 2023 kl 23:35 skrev Maxim Cournoyer < maxim.courno...@gmail.com>: > Hello, > > Nathan Hartman <hartman.nat...@gmail.com> writes: > > > On Thu, Mar 30, 2023 at 11:13 PM Maxim Cournoyer > > <maxim.courno...@gmail.com> wrote: > [...] I assume the log is from this build: > And on an old 4 cores desktop: > > --8<---------------cut here---------------start------------->8--- > At least one test FAILED, checking > /tmp/guix-build-subversion-1.14.2.drv-0/subversion-1.14.2/tests.log > FAIL: fs-fs-pack-test: Unknown test failure (-6); see tests.log. > fs-fs-pack-test: subversion/libsvn_subr/utf.c:424: put_xlate_handle_node: Assertion `node->next == NULL' failed. > FAIL: fs-test: Unknown test failure (-6); see tests.log. > fs-test: subversion/libsvn_subr/utf.c:424: put_xlate_handle_node: Assertion `node->next == NULL' failed. > FAIL: io-test: Unknown test failure (-6); see tests.log. > io-test: subversion/libsvn_subr/utf.c:424: put_xlate_handle_node: Assertion `node->next == NULL' failed. > FAIL: op-depth-test: Unknown test failure (-6); see tests.log. > op-depth-test: subversion/libsvn_subr/utf.c:424: put_xlate_handle_node: Assertion `node->next == NULL' failed. There is some mutex handling in utf.c. I'm thinking if APR is missing the appropriate mutex handling in some weird way. What is the exact versions of APR/APR-util in your builld? FAIL: repos-test 2: test deletions under copies in node_tree code > svn_tests: E000002: Repository creation failed svn_tests: E000002: Creating db lock file svn_tests: E000002: Can'FAIL: repos-test 1: test svn_repos_dir_delta2 svn_tests: E000002: Repository creation failed svn_tests: E000002: Creating db logs lock file svn_tests: E000002: Can't open file '/tmp/guix-build-subversion-1.14.2.drv-0/subversion-1.14.2/subversion/tests/libsvn_repos/test-repo-del-under-copy/locks/db-logs.lock': No such file or directory FAIL: repos-test 2: test deletions under copies in node_tree code > FAIL: repos-test 3: test svn_repos_history() (partially) > svn_tests: E000002: Repository creation failed svn_tests: E000002: Creating lock dir svn_tests: E000002: Can't create directory '/tmp/guix-build-subversion-1.14.2.drv-0/subversion-1.14.2/subversion/tests/libsvn_repos/test-repo-revisions-changed/locks': No such file or directory FAIL: repos-test 3: test svn_repos_history() (partially) FAIL: repos-test 5: test svn_repos_node_locations some more > svn_tests: E000002: Repository creation failed svn_tests: E000002: Creating pre-commit hook svn_tests: E000002: Can't change perms of file '/tmp/guix-build-subversion-1.14.2.drv-0/subversion-1.14.2/subversion/tests/libsvn_repos/test-repo-node-locations2/hooks/pre-commit.tmpl': No such file or directory FAIL: repos-test 5: test svn_repos_node_locations some more > FAIL: repos-test: Unknown test failure (-11); see tests.log. > Since each test operate on its own WC, I can't really figure out why there would be issues with these tests, unless there is an error in svn_atomic_inc() (see subversion/tests/svn_test_main.c, test_thread()) causing the same test to be started more than once (by separate threads). > So the failures appear to be non-deterministic, although some test suite > such as repos-test fail more often than not. > What is the exact OS (distribution/release/kernel version) you are running? Kind regards, Daniel Sahlberg
