You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Nathan Hartman <ha...@gmail.com> on 2026/01/15 16:48:01 UTC
Re: [GH] (subversion/trunk): Workflow run "autoconf" failed!
On Thu, Jan 15, 2026 at 9:50 AM GitBox <gi...@apache.org> wrote:
>
> The GitHub Actions job "autoconf" on subversion.git/trunk has failed.
> Run started by GitHub user asf-gitbox-commits (triggered by
> asf-gitbox-commits).
>
> Head commit for run:
> 2126567c6462bd1d1f246cfda5989fbd313f14ab / Evgeny Kotkov <
> kotkov@apache.org>
> * CHANGES: Draft initial changelog for 1.15.0.
>
>
> git-svn-id: https://svn.apache.org/repos/asf/subversion/trunk@1931332
> 13f79535-47bb-0310-9956-ffa450edef68
>
> Report URL: https://github.com/apache/subversion/actions/runs/21034688896
>
> With regards,
> GitHub Actions via GitBox
I haven't dug into this yet, but I've collected the relevant logs from
GHA here (because they are kept only for a limited time):
The test failure occurs on ubuntu-latest, target davautocheck, system
httpd. (The test appears to succeed on ARM64 as shown below.)
(snip)
At least one test FAILED, checking
/home/runner/work/subversion/subversion/tests.log
FAIL: ra-test: Unknown test failure (-11); see tests.log.
There were some XML validation errors,
checking/home/runner/work/subversion/subversion/tests.log
XML: Opening and ending tag mismatch: log line 2 and logentry, line 3,
column 12 (<string>, line 3)
Summary of test results:
2636 tests PASSED
97 tests SKIPPED
82 tests XFAILED (17 WORK-IN-PROGRESS)
1 test FAILED
Python version: 3.12.3.
SUMMARY: Some tests failed
make[1]: *** [Makefile:553: check] Error 1
make[1]: Leaving directory '/home/runner/work/subversion/subversion'
davautocheck.sh: Finished testing...
real 8m43.165s
user 13m27.654s
sys 11m25.937s
davautocheck.sh: Browse server access log (y/n)? [n]
davautocheck.sh: Browse server error log (y/n)? [n]
davautocheck.sh: Delete HTTPD root directory (y/n)? [y]
davautocheck.sh: Done
make: *** [Makefile:662: davautocheck] Error 2
(snip)
For comparison, this is what it looks like on ARM64
(tests-ubuntu-22.04-arm-check-system.log), where the test succeeds:
(snip)
START: ra-test
PASS: ra-test 2: test ra_svn tunnel callback check
PASS: ra-test 3: test ra_svn tunnel creation callbacks
PASS: ra-test 1: test svn_ra_get_location_segments
PASS: ra-test 6: commit callback failure
PASS: ra-test 5: test ra_get_dir2
PASS: ra-test 7: base revision newer than youngest
PASS: ra-test 4: lock multiple paths
PASS: ra-test 8: delete revision newer than youngest
PASS: ra-test 10: check how ra layers handle errors from callbacks
PASS: ra-test 9: check how ra functions handle bad revisions
PASS: ra-test 12: verify checkout over a tunnel
PASS: ra-test 13: check how last change applies to empty commit
PASS: ra-test 15: test get-deleted-rev no delete
PASS: ra-test 14: check commit editor for a locked file
PASS: ra-test 16: test get-deleted-rev errors
PASS: ra-test 11: check list has_props performance
END: ra-test
ELAPSED: ra-test 0:00:02.967689
(snip)
Now this is what it looks like at
tests-ubuntu-latest-davautocheck-system.log where the test fails:
(snip)
START: ra-test
TEST ASSERTION FAILED: child_exit_code == 0
PASS: ra-test 2: test ra_svn tunnel callback check
PASS: ra-test 1: test svn_ra_get_location_segments
PASS: ra-test 5: test ra_get_dir2
PASS: ra-test 6: commit callback failure
PASS: ra-test 7: base revision newer than youngest
PASS: ra-test 8: delete revision newer than youngest
PASS: ra-test 4: lock multiple paths
PASS: ra-test 10: check how ra layers handle errors from callbacks
PASS: ra-test 9: check how ra functions handle bad revisions
PASS: ra-test 12: verify checkout over a tunnel
PASS: ra-test 13: check how last change applies to empty commit
PASS: ra-test 14: check commit editor for a locked file
PASS: ra-test 16: test get-deleted-rev errors
PASS: ra-test 15: test get-deleted-rev no delete
FAIL: ra-test: Unknown test failure (-11); see tests.log.
END: ra-test
ELAPSED: ra-test 0:00:00.676186
(snip)
So it would appear ra-test 11 is having a bit of trouble. I hope I can
reproduce it locally...
Cheers,
Nathan
Re: [GH] (subversion/trunk): Workflow run "autoconf" failed!
Posted by Jun Omae <ju...@gmail.com>.
On Fri, Jan 16, 2026 at 4:12 AM Branko Čibej <br...@apache.org> wrote:
>
> -11 is the exit code. On Linux, signal 11 is SIGSEGV, so something is trying to access an invalid memory address. This might be happening in ra-test 11 (what a coincidence) or it may be that some test setup or teardown in ra-test leaves dirty data lying around.
>
> I've seen this very intermittently while testing on arm64 macOS, but have never been able to reproduce it consistently.
>
> -- Brane
It is able to reproduce the issue at 1 - 4 % while running ra-test
repeatedly, on both Ubuntu and macOS. According to the crash reports
(attached), it seems that the ra-test crashes on call apr_proc_create()
to open a tunnel while cleanup in serf_default_destroy_and_data().
[[[
$ t=subversion/tests/libsvn_ra/ra-test
$ make davautocheck PARALLEL=12 APACHE_MPM=event TESTS="$t $t $t $t $t
$t $t $t $t $t $t $t $t $t $t $t $t $t $t $t $t $t $t $t"
davautocheck.sh: Using '/usr/local/opt/httpd/bin/apxs'...
davautocheck.sh: Using '/usr/local/opt/httpd/bin/htpasswd'...
davautocheck.sh: Monolithic Auth module not found. Assuming we run
against Apache 2.1+
davautocheck.sh: Found modules for Apache 2.3.0+
davautocheck.sh: Using directory
'/Users/groove/src/subversion.git/subversion/tests/cmdline/httpd-20260116-150607'...
davautocheck.sh: Adding users for lock authentication
Adding password for user jrandom
Adding password for user jconstant
Adding password for user __dumpster__
Adding password for user JRANDOM
Adding password for user JCONSTANT
davautocheck.sh: Adding groups for mod_authz_svn tests
Syntax OK
davautocheck.sh: HTTPD 2.4.63 started and listening on
'http://localhost:3691'...
davautocheck.sh: HTTPD is good
davautocheck.sh: starting the tests...
davautocheck.sh: Using default dav library
[01/24] ra-test..............................................................................................................success
[02/24] ra-test..............................................................................................................success
[03/24] ra-test..............................................................................................................success
[04/24] ra-test..............................................................................................................success
[05/24] ra-test..............................................................................................................success
[06/24] ra-test..............................................................................................................success
[07/24] ra-test..............................................................................................................success
[08/24] ra-test..............................................................................................................success
[09/24] ra-test..............................................................................................................success
[10/24] ra-test..............................................................................................................success
[11/24] ra-test..............................................................................................................success
[12/24] ra-test..............................................................................................................success
[13/24] ra-test..............................................................................................................success
[14/24] ra-test..............................................................................................................success
[15/24] ra-test.......................................................FAILURE
[16/24] ra-test..............................................................................................................success
[17/24] ra-test..............................................................................................................success
[18/24] ra-test..............................................................................................................success
[19/24] ra-test..............................................................................................................success
[20/24] ra-test..............................................................................................................success
[21/24] ra-test..............................................................................................................success
[22/24] ra-test..............................................................................................................success
[23/24] ra-test..............................................................................................................success
[24/24] ra-test..............................................................................................................success
At least one test FAILED, checking /Users/groove/src/subversion.git/tests.log
FAIL: ra-test: Unknown test failure (-11); see tests.log.
Summary of test results:
376 tests PASSED
1 test FAILED
Python version: 3.13.5.
SUMMARY: 😱 Some tests failed
make[1]: *** [check] Error 1
real 5m34.195s
user 0m4.348s
sys 0m10.843s
davautocheck.sh: Finished testing...
davautocheck.sh: Browse server access log (y/n)? [n]
davautocheck.sh: Browse server error log (y/n)? [n]
davautocheck.sh: Delete HTTPD root directory (y/n)? [y]
davautocheck.sh: Done
make: *** [davautocheck] Error 2
]]]
[[[
START: ra-test
TEST ASSERTION FAILED: child_exit_code == 0
PASS: ra-test 2: test ra_svn tunnel callback check
PASS: ra-test 3: test ra_svn tunnel creation callbacks
PASS: ra-test 1: test svn_ra_get_location_segments
PASS: ra-test 6: commit callback failure
PASS: ra-test 7: base revision newer than youngest
PASS: ra-test 5: test ra_get_dir2
PASS: ra-test 8: delete revision newer than youngest
PASS: ra-test 4: lock multiple paths
FAIL: ra-test: Unknown test failure (-11); see tests.log.
END: ra-test
ELAPSED: ra-test 0:00:03.222153
]]]
--
Jun Omae <ju...@gmail.com> (大前 潤)
Re: [GH] (subversion/trunk): Workflow run "autoconf" failed!
Posted by Branko Čibej <br...@apache.org>.
On 15. 1. 26 17:48, Nathan Hartman wrote:
> On Thu, Jan 15, 2026 at 9:50 AM GitBox <gi...@apache.org> wrote:
>
>
> The GitHub Actions job "autoconf" on subversion.git/trunk has failed.
> Run started by GitHub user asf-gitbox-commits (triggered by
> asf-gitbox-commits).
>
> Head commit for run:
> 2126567c6462bd1d1f246cfda5989fbd313f14ab / Evgeny Kotkov
> <ko...@apache.org>
> * CHANGES: Draft initial changelog for 1.15.0.
>
>
> git-svn-id:
> https://svn.apache.org/repos/asf/subversion/trunk@1931332
> 13f79535-47bb-0310-9956-ffa450edef68
>
> Report URL:
> https://github.com/apache/subversion/actions/runs/21034688896
>
> With regards,
> GitHub Actions via GitBox
>
>
>
> I haven't dug into this yet, but I've collected the relevant logs from
> GHA here (because they are kept only for a limited time):
>
> The test failure occurs on ubuntu-latest, target davautocheck, system
> httpd. (The test appears to succeed on ARM64 as shown below.)
>
> (snip)
> At least one test FAILED, checking
> /home/runner/work/subversion/subversion/tests.log
> FAIL: ra-test: Unknown test failure (-11); see tests.log.
> There were some XML validation errors,
> checking/home/runner/work/subversion/subversion/tests.log
> XML: Opening and ending tag mismatch: log line 2 and logentry, line 3,
> column 12 (<string>, line 3)
> Summary of test results:
> 2636 tests PASSED
> 97 tests SKIPPED
> 82 tests XFAILED (17 WORK-IN-PROGRESS)
> 1 test FAILED
> Python version: 3.12.3.
> SUMMARY: Some tests failed
[...]
> (snip)
> START: ra-test
> TEST ASSERTION FAILED: child_exit_code == 0
> PASS: ra-test 2: test ra_svn tunnel callback check
> PASS: ra-test 1: test svn_ra_get_location_segments
> PASS: ra-test 5: test ra_get_dir2
> PASS: ra-test 6: commit callback failure
> PASS: ra-test 7: base revision newer than youngest
> PASS: ra-test 8: delete revision newer than youngest
> PASS: ra-test 4: lock multiple paths
> PASS: ra-test 10: check how ra layers handle errors from callbacks
> PASS: ra-test 9: check how ra functions handle bad revisions
> PASS: ra-test 12: verify checkout over a tunnel
> PASS: ra-test 13: check how last change applies to empty commit
> PASS: ra-test 14: check commit editor for a locked file
> PASS: ra-test 16: test get-deleted-rev errors
> PASS: ra-test 15: test get-deleted-rev no delete
> FAIL: ra-test: Unknown test failure (-11); see tests.log.
> END: ra-test
> ELAPSED: ra-test 0:00:00.676186
> (snip)
>
> So it would appear ra-test 11 is having a bit of trouble. I hope I can
> reproduce it locally...
-11 is the exit code. On Linux, signal 11 is SIGSEGV, so something is
trying to access an invalid memory address. This might be happening in
ra-test 11 (what a coincidence) or it may be that some test setup or
teardown in ra-test leaves dirty data lying around.
I've seen this very intermittently while testing on arm64 macOS, but
have never been able to reproduce it consistently.
-- Brane
Re: [GH] (subversion/trunk): Workflow run "autoconf" failed!
Posted by Jun Omae <ju...@gmail.com>.
I've collected the full backtrace of the issue which is reproduced locally.
See
https://lists.apache.org/thread/9vjpg8hqgd5b81x9y8lvz5dv4z2rr3zo
Jun Omae <ju...@gmail.com> (大前 潤)
On Fri, Jan 16, 2026 at 1:48 Nathan Hartman <ha...@gmail.com>
wrote:
> On Thu, Jan 15, 2026 at 9:50 AM GitBox <gi...@apache.org> wrote:
>
>>
>> The GitHub Actions job "autoconf" on subversion.git/trunk has failed.
>> Run started by GitHub user asf-gitbox-commits (triggered by
>> asf-gitbox-commits).
>>
>> Head commit for run:
>> 2126567c6462bd1d1f246cfda5989fbd313f14ab / Evgeny Kotkov <
>> kotkov@apache.org>
>> * CHANGES: Draft initial changelog for 1.15.0.
>>
>>
>> git-svn-id: https://svn.apache.org/repos/asf/subversion/trunk@1931332
>> 13f79535-47bb-0310-9956-ffa450edef68
>>
>> Report URL: https://github.com/apache/subversion/actions/runs/21034688896
>>
>> With regards,
>> GitHub Actions via GitBox
>
>
>
> I haven't dug into this yet, but I've collected the relevant logs from
> GHA here (because they are kept only for a limited time):
>
> The test failure occurs on ubuntu-latest, target davautocheck, system
> httpd. (The test appears to succeed on ARM64 as shown below.)
>
> (snip)
> At least one test FAILED, checking
> /home/runner/work/subversion/subversion/tests.log
> FAIL: ra-test: Unknown test failure (-11); see tests.log.
> There were some XML validation errors,
> checking/home/runner/work/subversion/subversion/tests.log
> XML: Opening and ending tag mismatch: log line 2 and logentry, line 3,
> column 12 (<string>, line 3)
> Summary of test results:
> 2636 tests PASSED
> 97 tests SKIPPED
> 82 tests XFAILED (17 WORK-IN-PROGRESS)
> 1 test FAILED
> Python version: 3.12.3.
> SUMMARY: Some tests failed
>
> make[1]: *** [Makefile:553: check] Error 1
> make[1]: Leaving directory '/home/runner/work/subversion/subversion'
>
> davautocheck.sh: Finished testing...
> real 8m43.165s
> user 13m27.654s
> sys 11m25.937s
> davautocheck.sh: Browse server access log (y/n)? [n]
> davautocheck.sh: Browse server error log (y/n)? [n]
> davautocheck.sh: Delete HTTPD root directory (y/n)? [y]
> davautocheck.sh: Done
> make: *** [Makefile:662: davautocheck] Error 2
> (snip)
>
> For comparison, this is what it looks like on ARM64
> (tests-ubuntu-22.04-arm-check-system.log), where the test succeeds:
>
> (snip)
> START: ra-test
> PASS: ra-test 2: test ra_svn tunnel callback check
> PASS: ra-test 3: test ra_svn tunnel creation callbacks
> PASS: ra-test 1: test svn_ra_get_location_segments
> PASS: ra-test 6: commit callback failure
> PASS: ra-test 5: test ra_get_dir2
> PASS: ra-test 7: base revision newer than youngest
> PASS: ra-test 4: lock multiple paths
> PASS: ra-test 8: delete revision newer than youngest
> PASS: ra-test 10: check how ra layers handle errors from callbacks
> PASS: ra-test 9: check how ra functions handle bad revisions
> PASS: ra-test 12: verify checkout over a tunnel
> PASS: ra-test 13: check how last change applies to empty commit
> PASS: ra-test 15: test get-deleted-rev no delete
> PASS: ra-test 14: check commit editor for a locked file
> PASS: ra-test 16: test get-deleted-rev errors
> PASS: ra-test 11: check list has_props performance
> END: ra-test
> ELAPSED: ra-test 0:00:02.967689
> (snip)
>
> Now this is what it looks like at
> tests-ubuntu-latest-davautocheck-system.log where the test fails:
>
> (snip)
> START: ra-test
> TEST ASSERTION FAILED: child_exit_code == 0
> PASS: ra-test 2: test ra_svn tunnel callback check
> PASS: ra-test 1: test svn_ra_get_location_segments
> PASS: ra-test 5: test ra_get_dir2
> PASS: ra-test 6: commit callback failure
> PASS: ra-test 7: base revision newer than youngest
> PASS: ra-test 8: delete revision newer than youngest
> PASS: ra-test 4: lock multiple paths
> PASS: ra-test 10: check how ra layers handle errors from callbacks
> PASS: ra-test 9: check how ra functions handle bad revisions
> PASS: ra-test 12: verify checkout over a tunnel
> PASS: ra-test 13: check how last change applies to empty commit
> PASS: ra-test 14: check commit editor for a locked file
> PASS: ra-test 16: test get-deleted-rev errors
> PASS: ra-test 15: test get-deleted-rev no delete
> FAIL: ra-test: Unknown test failure (-11); see tests.log.
> END: ra-test
> ELAPSED: ra-test 0:00:00.676186
> (snip)
>
> So it would appear ra-test 11 is having a bit of trouble. I hope I can
> reproduce it locally...
>
> Cheers,
> Nathan
>
>