You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Ben Reser <be...@reser.org> on 2015/03/06 01:09:11 UTC
1.9.0-beta1 up for testing/signing
The 1.9.0-beta1 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.
Please keep in mind that this is a beta and that it's going to take a
significant blocker to want to avoid releasing it (e.g. something that destroys
data).
Re: 1.9.0-beta1 up for testing/signing
Posted by Johan Corveleyn <jc...@gmail.com>.
On Wed, Mar 11, 2015 at 3:00 PM, Johan Corveleyn <jc...@gmail.com> wrote:
> On Fri, Mar 6, 2015 at 1:09 AM, Ben Reser <be...@reser.org> wrote:
>> The 1.9.0-beta1 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.
>>
>> Please keep in mind that this is a beta and that it's going to take a
>> significant blocker to want to avoid releasing it (e.g. something that destroys
>> data).
>
> FWIW, I fully intend to participate in testing (and hopefully signing)
> this beta on Windows. I've had some personal distractions, and then
> some difficulties getting everything set up on the new laptop (I first
> tried with Windows 8.1, but I got so frustrated with it that I
> reformatted and installed Windows 7 ... I'm more used to that). But
> I'm slowly getting there ... It'll take me a couple more days I guess.
>
A bit late to the party, but now I know I have a working build / test
environment again:
Summary
-------
+1 to release
Platform
--------
Windows 7 SP1 (x64)
Microsoft Visual Studio 2013
Verified
--------
Signature and sha1 for subversion-1.9.0-beta1.zip.
Contents of subversion-1.9.0-beta1.zip are identical to tags/1.9.0-beta1, and
to branches/1.9.x@1664469 (except for expected differences in svn_version.h
and svnpubsub, svnwcsub and nominate.pl (symlinks vs. file contents), and
generated files).
Tested
------
[ Release build ] x [ fsfs ] x [ file | svn | http ]
Results
-------
All tests pass.
Dependencies
------------
Httpd 2.4.12
Apr 1.5.1
Apr-Util 1.5.4
OpenSSL 1.0.2
Serf 1.3.8
SQLite 3.8.8.3
ZLib 1.2.8
Signature
---------
subversion-1.9.0-beta1.zip:
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAABCgAGBQJVCNAbAAoJELWc5tYBDIqtihcP/2ia9DaLaNpDSOBA12adtUG6
nKYNCBAgbtIC6bH5O295rsIDVaWrvcVexcl/rrDv6sgyIN1jQM2zvYKF1r6F4ntF
seGj5VVZGSLR5P4s1JEjYGwZedJMU2vVq7ZPTRboz8bGoVjCSrm4CcGZY/Niln57
hLXNwGCzqast/BqUHie6ZWgeJ0dkN61+YAJVANNj08aSPJN/nLK5C1rxlTIxqwhJ
TfnY6mSLTicEvuqbMlqXXPMn3QvdBXB8lmYmNngJAaSBSQFUsyxZARYmBLyYht8X
XPso6eIG6ugOl38B0DpNQCz0qrmH9c5rdrYHifAj7JIB+HKjG+IcVWIo6aaYWyyK
M/eAIZ3za/P2JZdmzi38yW5yVPydZ5gZxZHjgxAeljdLje9YaCtDilKYbEkkDPN5
q1WxBUMShv8cHVBValTUy4Vgr4sU5ynnCZFowcoiKTEgXT+jH7Aav39129iTbMdq
It0kfhzqnmr6Klh6kiP5fahbKCqbyvYCAvnlqG+fFSGki0JxsXpxjwLwHMt2DmK9
VtAApr9jtcltM90A1KGrfQ1Bylp4rf2B712Vb3WFDKWE8pxXJ7N7Sr4OOBpt+CrG
XnIiMGj4wb7M5aIuQva9ZNkEcFftL4ltfwCK6LB5P3Rv1n9H0YZOUX54QpN12zXT
XAyqqRN8Am3SNJkZhDwj
=Negp
-----END PGP SIGNATURE-----
--
Johan
Re: 1.9.0-beta1 up for testing/signing
Posted by Johan Corveleyn <jc...@gmail.com>.
On Fri, Mar 6, 2015 at 1:09 AM, Ben Reser <be...@reser.org> wrote:
> The 1.9.0-beta1 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.
>
> Please keep in mind that this is a beta and that it's going to take a
> significant blocker to want to avoid releasing it (e.g. something that destroys
> data).
FWIW, I fully intend to participate in testing (and hopefully signing)
this beta on Windows. I've had some personal distractions, and then
some difficulties getting everything set up on the new laptop (I first
tried with Windows 8.1, but I got so frustrated with it that I
reformatted and installed Windows 7 ... I'm more used to that). But
I'm slowly getting there ... It'll take me a couple more days I guess.
--
Johan
Re: 1.9.0-beta1 up for testing/signing
Posted by Branko Čibej <br...@wandisco.com>.
Summary:
+1 to release
Despite the heisenbug (see below), I think we can release
this as a beta. The bug itself is a 1.9.0 release blocker.
Platform
Mac OS X 10.10.2 Yosemite, build 14C109
Standard dependencies:
Apple LLVM version 6.0 (clang-600.0.56) (based on LLVM 3.5svn)
APR 1.4.8
APR-Util 1.5.2
zlib 1.2.5
httpd 2.4.9
Python 2.7.6
Perl 5.18.2
ruby 2.0.0p481 (2014-05-08 revision 45883)
SQLite 3.8.5
Dependencies from homebrew:
SQLite 3.8.8.3
Serf 1.3.8
OpenSSL 1.0.2
BDB 6.1.19
libmagic 5.22
Other dependencies:
Swig 2.0.12
Java 1.8.0_25-b17
JUnit 4.11
Verified:
Tarball contents and signatures
(fsfs, bdb) x (local, svnserve, dav) with SQLite 3.8.8.3
(fsfs) x (local) with SQLite 3.8.5
check-all-javahl
check-swig-py
check-swig-rb
check-swig-pl
New issues:
- iprop_tests.py #3 failed during an update with a SIGBUS on
ra_svn+fsfs during the first test iteration. It succeeded during
subsequent re-tests. I also got random failures during a commit
in the same configuration in merge_authz_tests.py #3.
This implies the existence of a heisenbug.
Known issues: None
GPG signatures committed to the dist/dev/subversion repository.
Re: 1.9.0-beta1 up for testing/signing
Posted by Philip Martin <ph...@wandisco.com>.
Summary:
+1 to release
Platform:
Linux (Debian/jessie) 64-bit
Tested:
(local, svn, svn/sasl, serf, serf/v1) x (fsfs, fsfs/pack/shard, bdb, fsx)
swig-pl, swig-py, swig-rb, ctypes-python
javahl x (fsfs, bdb, fsx)
local x (fsfs-v4, fsfs-v6)
Results:
FAIL svnadmin_tests.py 33 and 34 with FSFS_SHARDING, testsuite bugs
FAIL ra-test 6 and externals_tests 57 with HTTPV1, fix proposed
All other tests PASS
Local dependencies:
libapr1-dev : 1.5.1-3
libaprutil1-dev : 1.5.4-1
libsasl2-dev : 2.1.26.dfsg1-12
libsqlite3-dev : 3.8.7.1-1
libdb5.3-dev : 5.3.28-9
perl : 5.20.1-5
python2.7-dev : 2.7.8-11
ruby-dev : 1:2.1.0.4
openjdk-7-jdk : 7u75-2.5.4-2
serf : 1.3.x@2474
subversion-1.9.0-beta1.tar.bz2
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAABCAAGBQJU/3QEAAoJEHbXiOHtGlmctusH/jOXJANI/wm9BP6S30lIBb9T
5eXJLxfhu0VRBO9BKdB86lqVqU9e8IotfcXVG6pNXHLCvj7p6cc4EMcRlnsIQdJX
WxSXXn3J2/1yVmDB9tee1h0ijSk/YC3KHfe8o63WrzwQMWfXDvSrfTROlm+YSidm
1EoSt8aNqmOfnLKU1YPdJpOwdaszJ/z0LbOMEoIK5UOEdQ5uqP1xgDBze0Tdsjcv
EYOHjYc2uKJzOuJDVBid9iz8dNYw6b1L8R9BvnYUeLoUoLNpcZfurFYmMhSZ62dL
31UD20DjfYulX5CeXXOOpkWCoWROvZsamJH68LXyKF6gEfFRcdIWdzt+81rJvgQ=
=Aa6P
-----END PGP SIGNATURE-----
subversion-1.9.0-beta1.tar.gz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAABCAAGBQJU/3QEAAoJEHbXiOHtGlmcws8H/0hEJgpy1tMiacIL/AiX8RVf
phOjii30SH+lFJ+Gw+gb4Vx5AyUHBVhYK9Uqxm3L6zUbtslIVpbM+IB1GR23XTns
oLQgq0Zh+pqPSnhKGC20W6jL4whMELSLP8W2x3P+/y9x7GUzEvSS2DeqHH5n5fzA
8mNpR5tqibn8xoLjD7hyfPX6nra80MGC6uSH92bOyHSIQLY3QOj/HDPW6i06c+SC
N03FXWTFHcGb9ROVfZXVRI25vmB2Os0Ph9aw7PyRtv/G36gwhFLW6BQsV19UhaDL
Pgvt+RnvDzscDSKNI+om70QY7LFLfwzoJP1O0ixqDTgf9bj/RXaT5Q64ikiaTMw=
=NDAD
-----END PGP SIGNATURE-----
--
Philip Martin | Subversion Committer
WANdisco // *Non-Stop Data*
Re: 1.9.0-beta1 up for testing/signing
Posted by Ben Reser <be...@reser.org>.
On 3/5/15 4:09 PM, Ben Reser wrote:
> The 1.9.0-beta1 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.
>
> Please keep in mind that this is a beta and that it's going to take a
> significant blocker to want to avoid releasing it (e.g. something that destroys
> data).
>
I'll be announcing 1.9.0-beta1 tomorrow. I'd forgotten we'd removed the 3 +1's
for each platform for alpha/betas and we were good when we'd gotten Bert's vote.
>From our community documentation:
[[[
For -alpha and -beta releases, we still require at least one +1 vote on each
major platform we support, but waive the requirement for three signers on each
platform. (The requirement for at least three signers in total remains.)
]]]
Re: 1.9.0-beta1 up for testing/signing
Posted by Julian Foad <ju...@btopenworld.com>.
Ben Reser wrote:
> The 1.9.0-beta1 release artifacts are now available for testing/signing.
SUMMARY:
--------
+1 to release (Unix)
VERIFIED:
---------
SHA1 sums:
cbc62b682e69254f57e40da316ebb7fcf998f56e subversion-1.9.0-beta1.tar.bz2
57142f460c51f334429569757974006f275240e8 subversion-1.9.0-beta1.tar.gz
Comparing the two compressions of each tar package:
Files subversion-1.9.0-beta1.tar(bz2) and subversion-1.9.0-beta1.tar(gz) are identical
TESTED:
-------
[ fsfs | bdb ] x [ file | svn | http (serf; MPM=worker) ]
swig-rb
swig-py (BUILT ONLY; NOT TESTED)
swig-pl
javahl
cytpes-python
RESULTS:
--------
All tests pass except:
I always get this failure in RA-serf tests:
FAIL: basic_tests.py 38: use folders with names like 'c:hi'
I understand that is due to a bug in my version of Apache HTTPD that is
resolved in newer versions, and a patch to make the test XFAIL for such
versions is already approved for backport.
I saw a one-time failure in testing with RA-serf and BDB:
FAIL: autoprop_tests.py 26: inherit import: config=no, commandline=no
Unfortunately I don't have the log output. I tried several times to
reproduce it and always got success. It's quite possible this failure was
caused by a local issue such as the computer going into 'suspend' mode
during the testing. I consider this unlikely to be a 'real' problem.
PLATFORM:
---------
Ubuntu 14.04 (Linux kernel: 3.13.0-45-generic x86_64)
DEPENDENCIES:
-------------
APR: 1.5.1
APR-UTIL: 1.5.3
zlib: 1.2.8
OpenSSL: 1.0.1
Apache: 2.4.7
BDB: 5.3.21
sqlite: 3.7.13
Python: 2.7.5/2.7.6
Perl: 5.18.2
Ruby: 1.9.3
java: 1.7.0
junit: 4.11
swig: 2.0.11
serf: 1.3.7
- Julian
RE: 1.9.0-beta1 up for testing/signing
Posted by Bert Huijben <be...@qqmail.nl>.
> -----Original Message-----
> From: Ben Reser [mailto:ben@reser.org]
> Sent: vrijdag 6 maart 2015 01:09
> To: Subversion Development
> Subject: 1.9.0-beta1 up for testing/signing
>
> The 1.9.0-beta1 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.
>
> Please keep in mind that this is a beta and that it's going to take a
> significant blocker to want to avoid releasing it (e.g. something that destroys
> data).
+1 for release
I actually switched all my Subversion clients to this beta version to dogfood the release, and I like how it behaves on Windows.
(Everything appears to go at least a bit faster... in many cases more than a bit)
I ran the usual tests
[bdb | fsfs] x [local | svn | serf | serf/httpv1]
This time including JavaHL
Windows 8.1, Visual Studio 2013
Windows 2012 R2, Visual Studio 2010
And after applying a few patches:
Windows 10 preview, Visual Studio 2015 CTP6.
And also did a full integration test in SharpSvn and then AnkhSVN.
(Toolchain: Windows Server 2008, Visual Studio 2008)
I found quite a list of things that in my eyes should be fixed before RC, see STATUS. But nothing that should delay this beta.
Bert
Re: [patch] Fix test failures with certain directory names (was:
1.9.0-beta1 up for testing/signing)
Posted by 'James McCoy' <ja...@debian.org>.
On Sun, Mar 08, 2015 at 03:32:35PM +0100, Bert Huijben wrote:
> > -----Original Message-----
> > From: James McCoy [mailto:jamessan@debian.org]
> > Sent: zondag 8 maart 2015 05:22
> > To: dev@subversion.apache.org
> > Subject: [patch] Fix test failures with certain directory names (was: 1.9.0-beta1
> > up for testing/signing)
> >
> > On Thu, Mar 05, 2015 at 04:09:11PM -0800, Ben Reser wrote:
> > > The 1.9.0-beta1 release artifacts are now available for testing/signing.
> >
> > I was testing this from within a directory named subversion-1.9.0~beta1
> > and a number of tests failed due to differences in whether the ~ was
> > URL-escaped. The attached patch fixes the issue for me.
>
> I applied a tweaked version of the patch in r1664997. Can you verify if this fixes the problems for you?
That does fix the problem. Thanks.
--
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy <ja...@debian.org>
RE: [patch] Fix test failures with certain directory names (was: 1.9.0-beta1 up for testing/signing)
Posted by Bert Huijben <be...@qqmail.nl>.
> -----Original Message-----
> From: James McCoy [mailto:jamessan@debian.org]
> Sent: zondag 8 maart 2015 05:22
> To: dev@subversion.apache.org
> Subject: [patch] Fix test failures with certain directory names (was: 1.9.0-beta1
> up for testing/signing)
>
> On Thu, Mar 05, 2015 at 04:09:11PM -0800, Ben Reser wrote:
> > The 1.9.0-beta1 release artifacts are now available for testing/signing.
>
> I was testing this from within a directory named subversion-1.9.0~beta1
> and a number of tests failed due to differences in whether the ~ was
> URL-escaped. The attached patch fixes the issue for me.
I applied a tweaked version of the patch in r1664997. Can you verify if this fixes the problems for you?
Your version of the patch somehow showed that we relied on some side effect of the quoting function to generate the urls on Windows. As a result I couldn't run a single python test.
With a few small tweaks I think I fixes those problems.
Thanks for your report + patch,
Bert
[patch] Fix test failures with certain directory names (was:
1.9.0-beta1 up for testing/signing)
Posted by James McCoy <ja...@debian.org>.
On Thu, Mar 05, 2015 at 04:09:11PM -0800, Ben Reser wrote:
> The 1.9.0-beta1 release artifacts are now available for testing/signing.
I was testing this from within a directory named subversion-1.9.0~beta1
and a number of tests failed due to differences in whether the ~ was
URL-escaped. The attached patch fixes the issue for me.
Cheers,
--
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy <ja...@debian.org>
Re: 1.9.0-beta1 up for testing/signing
Posted by Stefan Fuhrmann <st...@wandisco.com>.
On Fri, Mar 6, 2015 at 12:50 PM, Stefan Fuhrmann <
stefan.fuhrmann@wandisco.com> wrote:
>
>
> On Fri, Mar 6, 2015 at 11:41 AM, Branko Čibej <br...@wandisco.com> wrote:
>
>> On 06.03.2015 01:09, Ben Reser wrote:
>> > The 1.9.0-beta1 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.
>> >
>> > Please keep in mind that this is a beta and that it's going to take a
>> > significant blocker to want to avoid releasing it (e.g. something that
>> destroys
>> > data).
>>
>> We appear to have a heisenbug again. I got this while running
>> svnserveautocheck with FSFS:
>>
>> W: CMD: /Volumes/svn-release-test/1.9.0-beta1/subversion/svn/svn up
>> svn-test-work/working_copies/iprop_tests-3 --config-dir
>> /Volumes/svn-release-test/1.9.0-beta1/subversion/tests/cmdline/svn-test-work/local_tmp/config
>> --password rayjandom --no-auth-cache --username jrandom terminated by
>> signal 10
>> W: CWD: /Volumes/svn-release-test/1.9.0-beta1/subversion/tests/cmdline
>> W: EXCEPTION: SVNProcessTerminatedBySignal
>> FAIL: iprop_tests.py 3: inherited properties in switched subtrees
>>
>
> Does it go away when r1663450 is applied?
> The pools containing the hashed structs get
> cleared but the hash still points to data in them.
>
Forget that. The fix is already part of beta1.
Sorry for the noise!
-- Stefan^2.
Re: 1.9.0-beta1 up for testing/signing
Posted by Stefan Fuhrmann <st...@wandisco.com>.
On Fri, Mar 6, 2015 at 11:41 AM, Branko Čibej <br...@wandisco.com> wrote:
> On 06.03.2015 01:09, Ben Reser wrote:
> > The 1.9.0-beta1 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.
> >
> > Please keep in mind that this is a beta and that it's going to take a
> > significant blocker to want to avoid releasing it (e.g. something that
> destroys
> > data).
>
> We appear to have a heisenbug again. I got this while running
> svnserveautocheck with FSFS:
>
> W: CMD: /Volumes/svn-release-test/1.9.0-beta1/subversion/svn/svn up
> svn-test-work/working_copies/iprop_tests-3 --config-dir
> /Volumes/svn-release-test/1.9.0-beta1/subversion/tests/cmdline/svn-test-work/local_tmp/config
> --password rayjandom --no-auth-cache --username jrandom terminated by
> signal 10
> W: CWD: /Volumes/svn-release-test/1.9.0-beta1/subversion/tests/cmdline
> W: EXCEPTION: SVNProcessTerminatedBySignal
> FAIL: iprop_tests.py 3: inherited properties in switched subtrees
>
Does it go away when r1663450 is applied?
The pools containing the hashed structs get
cleared but the hash still points to data in them.
-- Stefan^2.
RE: 1.9.0-beta1 up for testing/signing
Posted by Bert Huijben <be...@qqmail.nl>.
> -----Original Message-----
> From: Philip Martin [mailto:philip.martin@wandisco.com]
> Sent: vrijdag 6 maart 2015 15:57
> To: Branko Čibej
> Cc: dev@subversion.apache.org
> Subject: Re: 1.9.0-beta1 up for testing/signing
>
> Philip Martin <ph...@wandisco.com> writes:
>
> > I'm seeing reproducible fails with FSFS_SHARDING=3
> >
> > $ nice make check TESTS=subversion/tests/cmdline/svnadmin_tests.py
> > FSFS_SHARDING=3
> > [1/1] svnadmin_tests.py..................................................FAILURE
> > At least one test was SKIPPED, checking
> /home/pm/sw/subversion/obj/tests.log
> > SKIP: svnadmin_tests.py 9: 'svnadmin hotcopy' checking db/format file
> > At least one test FAILED, checking /home/pm/sw/subversion/obj/tests.log
> > FAIL: svnadmin_tests.py 33: detect invalid changed path list entries
> > FAIL: svnadmin_tests.py 34: detect denormalized names and name collisions
> >
> > The tests don't handle the variations in "svnadmin verify" output caused
> > by different sharding.
>
> That's just a testsuite bug, I'm also seeing reproducible failures with
> the davautocheck and USE_HTTPV1=1:
>
> FAIL: lt-ra-test 6: commit callback failure
> FAIL: externals_tests.py 57: svn copy --pin-externals wc->repos
>
> The externals one is a client SEGV on commit.
Easy to reproduce on Windows as it immediately generated a good stacktrace via our crash handler.
Problem is fixed in r1664653.
The problem is 100% related to pinning externals, and I can confirm that it only accepts pre-HTTPv2 dav.
Bert
Re: 1.9.0-beta1 up for testing/signing
Posted by Philip Martin <ph...@wandisco.com>.
Philip Martin <ph...@wandisco.com> writes:
> I'm seeing reproducible fails with FSFS_SHARDING=3
>
> $ nice make check TESTS=subversion/tests/cmdline/svnadmin_tests.py
> FSFS_SHARDING=3
> [1/1] svnadmin_tests.py..................................................FAILURE
> At least one test was SKIPPED, checking /home/pm/sw/subversion/obj/tests.log
> SKIP: svnadmin_tests.py 9: 'svnadmin hotcopy' checking db/format file
> At least one test FAILED, checking /home/pm/sw/subversion/obj/tests.log
> FAIL: svnadmin_tests.py 33: detect invalid changed path list entries
> FAIL: svnadmin_tests.py 34: detect denormalized names and name collisions
>
> The tests don't handle the variations in "svnadmin verify" output caused
> by different sharding.
That's just a testsuite bug, I'm also seeing reproducible failures with
the davautocheck and USE_HTTPV1=1:
FAIL: lt-ra-test 6: commit callback failure
FAIL: externals_tests.py 57: svn copy --pin-externals wc->repos
The externals one is a client SEGV on commit.
--
Philip Martin | Subversion Committer
WANdisco // *Non-Stop Data*
Re: 1.9.0-beta1 up for testing/signing
Posted by Philip Martin <ph...@wandisco.com>.
Branko Čibej <br...@wandisco.com> writes:
> On 06.03.2015 01:09, Ben Reser wrote:
>> The 1.9.0-beta1 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.
>>
>> Please keep in mind that this is a beta and that it's going to take a
>> significant blocker to want to avoid releasing it (e.g. something
>> that destroys
>> data).
>
> We appear to have a heisenbug again. I got this while running
> svnserveautocheck with FSFS:
>
> W: CMD: /Volumes/svn-release-test/1.9.0-beta1/subversion/svn/svn up
> svn-test-work/working_copies/iprop_tests-3 --config-dir
> /Volumes/svn-release-test/1.9.0-beta1/subversion/tests/cmdline/svn-test-work/local_tmp/config
> --password rayjandom --no-auth-cache --username jrandom terminated by
> signal 10
> W: CWD: /Volumes/svn-release-test/1.9.0-beta1/subversion/tests/cmdline
> W: EXCEPTION: SVNProcessTerminatedBySignal
> FAIL: iprop_tests.py 3: inherited properties in switched subtrees
I'm seeing reproducible fails with FSFS_SHARDING=3
$ nice make check TESTS=subversion/tests/cmdline/svnadmin_tests.py FSFS_SHARDING=3
[1/1] svnadmin_tests.py..................................................FAILURE
At least one test was SKIPPED, checking /home/pm/sw/subversion/obj/tests.log
SKIP: svnadmin_tests.py 9: 'svnadmin hotcopy' checking db/format file
At least one test FAILED, checking /home/pm/sw/subversion/obj/tests.log
FAIL: svnadmin_tests.py 33: detect invalid changed path list entries
FAIL: svnadmin_tests.py 34: detect denormalized names and name collisions
The tests don't handle the variations in "svnadmin verify" output caused
by different sharding.
--
Philip Martin | Subversion Committer
WANdisco // *Non-Stop Data*
Re: 1.9.0-beta1 up for testing/signing
Posted by Branko Čibej <br...@wandisco.com>.
On 06.03.2015 01:09, Ben Reser wrote:
> The 1.9.0-beta1 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.
>
> Please keep in mind that this is a beta and that it's going to take a
> significant blocker to want to avoid releasing it (e.g. something that destroys
> data).
We appear to have a heisenbug again. I got this while running
svnserveautocheck with FSFS:
W: CMD: /Volumes/svn-release-test/1.9.0-beta1/subversion/svn/svn up svn-test-work/working_copies/iprop_tests-3 --config-dir /Volumes/svn-release-test/1.9.0-beta1/subversion/tests/cmdline/svn-test-work/local_tmp/config --password rayjandom --no-auth-cache --username jrandom terminated by signal 10
W: CWD: /Volumes/svn-release-test/1.9.0-beta1/subversion/tests/cmdline
W: EXCEPTION: SVNProcessTerminatedBySignal
FAIL: iprop_tests.py 3: inherited properties in switched subtrees
(that was a SIGBUS on OSX)
-- Brane
Re: 1.9.0-beta1 up for testing/signing
Posted by Ben Reser <be...@reser.org>.
On 3/10/15 2:40 AM, Stefan Fuhrmann wrote:
> basic_tests.py 38 failed over ra_serf due to faulty mod_dav;
> the version check introduced in r1639507 seems incomplete
r1665611 expands the versions set to XFAIL to include all the versions impacted
by Apache httpd PR 55397 and PR 56480. I'll nominate this for backport.
Re: 1.9.0-beta1 up for testing/signing
Posted by Stefan Fuhrmann <st...@wandisco.com>.
On Fri, Mar 6, 2015 at 1:12 PM, Stefan Fuhrmann <
stefan.fuhrmann@wandisco.com> wrote:
> On Fri, Mar 6, 2015 at 1:09 AM, Ben Reser <be...@reser.org> wrote:
>
>> The 1.9.0-beta1 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.
>>
>> Please keep in mind that this is a beta and that it's going to take a
>> significant blocker to want to avoid releasing it (e.g. something that
>> destroys
>> data).
>>
>
> I see basic_tests.py 38 fail consistently for serf 1.3.6
> over all FS types but no failure for other RA layers.
>
> I'll retest with the latest serf later today.
>
That one turned out to be a known issue with mod_dav
in Apache 2.4.7. Test test has been XFAIL in the past.
Summary:
+1 to release
Platform
Ubuntu 14.04.1 x64, Linux 3.16.0-31-generic SMP
Standard dependencies:
APR 1.5.0
APR-Util 1.5.3
BDB 5.3.28
GCC 4.8.2
httpd 2.4.7, worker MPM
JUnit 4.11
libmagic 5.14
libtool 2.4.2
neon 0.30.0
OpenJDK-7 7u51
OpenSSL 1.0.1f
Perl 5.18.2
Python 2.7.5
Ruby 1.9.3
SQLite 3.8.2
Swig 2.0.11
zlib 1.2.8
Manually installed and in-tree dependencies:
Serf 1.3.8
ctypesgen svn-r151
Verified:
Tarball contents and signatures
(fsfs, bdb, fsx) x (local, svnserve, serf)
check-swig-py
check-swig-pl
check-swig-rb
check-javahl
check-ctypes-python
./get-deps.sh
Results:
basic_tests.py 38 failed over ra_serf due to faulty mod_dav;
the version check introduced in r1639507 seems incomplete
All other tests passed.
GPG Signatures committed to the dist/dev/subversion repository.
-- Stefan^2.
Re: 1.9.0-beta1 up for testing/signing
Posted by Stefan Fuhrmann <st...@wandisco.com>.
On Fri, Mar 6, 2015 at 1:09 AM, Ben Reser <be...@reser.org> wrote:
> The 1.9.0-beta1 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.
>
> Please keep in mind that this is a beta and that it's going to take a
> significant blocker to want to avoid releasing it (e.g. something that
> destroys
> data).
>
I see basic_tests.py 38 fail consistently for serf 1.3.6
over all FS types but no failure for other RA layers.
I'll retest with the latest serf later today.
-- Stefan^2.