You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Hyrum K Wright <hy...@hyrumwright.org> on 2011/06/03 21:12:07 UTC
1.7.0-alpha1 tarballs up for testing/signing
All,
At long request, we now have tarballs for the first 1.7.0 pre-release:
1.7.0-alpha1 ("phoenix-hatchling"). These were cut from trunk, and
the magic rev is r1130808. The buildbots were green at that rev, and
all tests pass for me locally. You can find them here:
http://people.apache.org/~hwright/svn/1.7.0-alpha1/
This is an alpha release, and there are obviously known issues. The
purpose is to give distributors and downstream consumers a concrete
milestone against which to test, as well as vet our release processes
on ASF infrastructure. As you may expect, these prereleases are
intended for intrepid users and testers only.
As a reminder, there have been a few changes in the release artifacts
since the 1.6.x series. We no longer distribute a deps tarball, but
instead provide a get-deps.sh script for folks who want to fetch the
dependencies. There is no longer a 'to-tigris' directory in the
candidate directory. We no longer computer md5sums of the tarballs,
but continue to provide sha1sums to verify integrity. (There's
probably other stuff I've forgotten.)
I hope to get signatures from folks by the end of Tuesday, June 7, and
then do the public announcement. Historically, we've not required a
full set of signatures for alphas and betas, but it would be nice to
get at least some coverage besides just my own. As you send in your
signature announcement, please note any issues you found with the
alpha release (these will be included in the public announcement).
Please send sigs here:
http://work.hyrumwright.org/pub/svn/collect_sigs.py
-Hyrum
RE: 1.7.0-alpha1 tarballs up for testing/signing
Posted by Bert Huijben <be...@qqmail.nl>.
> -----Original Message-----
> From: Hyrum K Wright [mailto:hyrum@hyrumwright.org]
> Sent: vrijdag 3 juni 2011 21:12
> To: Subversion Development
> Subject: 1.7.0-alpha1 tarballs up for testing/signing
>
> All,
>
> At long request, we now have tarballs for the first 1.7.0 pre-release:
> 1.7.0-alpha1 ("phoenix-hatchling"). These were cut from trunk, and
> the magic rev is r1130808. The buildbots were green at that rev, and
> all tests pass for me locally. You can find them here:
> http://people.apache.org/~hwright/svn/1.7.0-alpha1/
>
> This is an alpha release, and there are obviously known issues. The
> purpose is to give distributors and downstream consumers a concrete
> milestone against which to test, as well as vet our release processes
> on ASF infrastructure. As you may expect, these prereleases are
> intended for intrepid users and testers only.
>
> As a reminder, there have been a few changes in the release artifacts
> since the 1.6.x series. We no longer distribute a deps tarball, but
> instead provide a get-deps.sh script for folks who want to fetch the
> dependencies. There is no longer a 'to-tigris' directory in the
> candidate directory. We no longer computer md5sums of the tarballs,
> but continue to provide sha1sums to verify integrity. (There's
> probably other stuff I've forgotten.)
>
> I hope to get signatures from folks by the end of Tuesday, June 7, and
> then do the public announcement. Historically, we've not required a
> full set of signatures for alphas and betas, but it would be nice to
> get at least some coverage besides just my own. As you send in your
> signature announcement, please note any issues you found with the
> alpha release (these will be included in the public announcement).
> Please send sigs here:
> http://work.hyrumwright.org/pub/svn/collect_sigs.py
By switching a development version of SharpSvn to trunk I identified the
following problems since this tag:
r1131052 - svn_repos_recover3 segfaults with a NULL callback.
r1131284 - svn_client_diff4 and svn_client_diff_peg4 pass invalid arguments
to their diff5 variants, thereby ignoring the ignore_content_type flag.
These problems don't impact our svn client, but are pretty serious for old
api users.
(I suggest not holding the release for them, but they belong in the release
notes)
I have a few more problems I'm investigating, but none of them look very
serious at this time.
r1131086 is also a direct result of this investigation: 'svn info
svn://localhost' used to provide 'Path: localhost' and now provides 'Path:
.'.
This difference is caused by switching from svn_path_basename to the more
correct svn_uri_basename.
Bert
Re: 1.7.0-alpha1 tarballs up for testing/signing
Posted by Senthil Kumaran S <st...@gmail.com>.
On Sun, Jun 5, 2011 at 9:21 AM, Senthil Kumaran S <st...@gmail.com> wrote:
> Oops, I am sorry for the spam! My email client screwed it up for every
> draft save :( The following is the correct email I intended to send.
Ignore the above, since my email client did not do anything wrong. It
was a false alarm!
Thank You.
--
Senthil Kumaran S
http://www.stylesen.org/
http://www.sasenthilkumaran.com/
Re: 1.7.0-alpha1 tarballs up for testing/signing
Posted by Senthil Kumaran S <st...@gmail.com>.
Oops, I am sorry for the spam! My email client screwed it up for every
draft save :( The following is the correct email I intended to send.
Thank You.
On Sun, Jun 5, 2011 at 9:18 AM, Senthil Kumaran S <st...@gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hyrum K Wright wrote:
>> At long request, we now have tarballs for the first 1.7.0 pre-release:
>> 1.7.0-alpha1 ("phoenix-hatchling"). These were cut from trunk, and
>> the magic rev is r1130808. The buildbots were green at that rev, and
>> all tests pass for me locally. You can find them here:
>> http://people.apache.org/~hwright/svn/1.7.0-alpha1/
>
> Summary:
>
> +1 to release (Unix) (though there are some problems with bindings.)
>
> Tested:
>
> 1.7.0-alpha1 ("phoenix-hatchling") tarball with local dependencies
> [ra_local, ra_svn, ra_serf, ra_neon] x [fsfs, bdb]
>
> Dependencies:
>
> APR 1.3.12
> APR-UTIL 1.3.9
> Apache httpd 2.2.15
> Neon 0.29.3
> Serf 0.7.2
> BDB 4.7.25
> OpenSSL 0.9.8o
> SunJDK 1.6.0_18
> SQLite 3.7.3
> JUnit 3.8.2
> Perl 5.10.1
> Python 2.6.6
> Ruby ruby 1.8.7 (2010-08-16 patchlevel 302)
> Swig 1.3.40
>
> Environment:
>
> Debian 6.0.1 (Squeeze - recently updated)
> Linux 2.6.32-5-686 #1 SMP i686 GNU/Linux
>
> Results:
>
> All tests PASSED!
>
> Bindings results:
>
> javahl Unable to compile. See [1] below.
>
> perl All tests successful.
> Files=10, Tests=214, 8 wallclock secs
> ( 0.07 usr 0.03 sys + 1.15 cusr 0.27 csys = 1.52 CPU)
> Result: PASS
>
> python Unable to compile. See [2] below.
>
> ruby Finished in 626.545453 seconds.
> 221 tests, 3169 assertions, 0 failures, 0 errors
>
> sha1sums (tested):
>
> 7710d703eb2365b2e91d66cedc4dbaab4ef6fbea subversion-1.7.0-alpha1.tar.bz2
> 212eaca54374a8e95ab5c6a15208870bbb339ae6 subversion-1.7.0-alpha1.tar.gz
>
> Verfied sha1sums (nothing more):
>
> e7f5456ccde81f0175eabc4af57e32f595d975e7 svn_version.h.dist
>
> GPG Signatures:
>
> subversion-1.7.0-alpha1.tar.bz2.asc
> - -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iEYEABECAAYFAk3q+rIACgkQ9o1G+2zNQDgglQCffMWgKNuGmlAkPQcfiFG0AVXR
> posAoIZO/RnMoyMtYQPdcdYNBSp6iOo+
> =78c2
> - -----END PGP SIGNATURE-----
>
> subversion-1.7.0-alpha1.tar.gz.asc
> - -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iEYEABECAAYFAk3q+r0ACgkQ9o1G+2zNQDjcawCbB+FrWy7hdP401c821FnCQ2NE
> o4QAmgO6EHgVLyBIZRlAA2iTiJlVgkcS
> =9GGm
> - -----END PGP SIGNATURE-----
>
> NOTE: Submitted signatures via webform too!
>
> [1] <http://people.apache.org/~stylesen/svn-1.7.0-alpha1/javahl-compile-error.txt>
> [2] <http://people.apache.org/~stylesen/svn-1.7.0-alpha1/swig-py-compile-error.txt>
>
> Thank You.
> - --
> Senthil Kumaran S
> http://www.stylesen.org/
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iEYEARECAAYFAk3q/JUACgkQ9o1G+2zNQDhXvQCfZhUHdfBVkCZN2QP5qCzVeJat
> 9t0AoL1e368TlxMGQHO+sumiKLZd80XW
> =7kmm
> -----END PGP SIGNATURE-----
>
--
Senthil Kumaran S
http://www.stylesen.org/
http://www.sasenthilkumaran.com/
Re: 1.7.0-alpha1 tarballs up for testing/signing
Posted by Senthil Kumaran S <st...@gmail.com>.
On Sun, Jun 5, 2011 at 9:28 PM, Daniel Shahaf <d....@daniel.shahaf.name> wrote:
> I have:
> * Debian stable
> * libc6-dev 2.11.2-10
> * /usr/lib/crti.o is reported (dpkg -S) to be owned by libc6-dev
I could see the above file,
<snip>
$ ls /usr/lib/crti.o -alh
-rw-r--r-- 1 root root 1012 Jan 24 05:40 /usr/lib/crti.o
</snip>
But for some reason 'make javahl' complains. I even tried uninstalling
'libc6-dev' and reinstalling it again.
When I do 'make javahl' it searches the files in the following directories:
<snip>
g++: /usr/lib/gcc/i486-linux-gnu/4.3.2/../../../../lib/crti.o: No such
file or directory
g++: /usr/lib/gcc/i486-linux-gnu/4.3.2/crtbeginS.o: No such file or directory
g++: /usr/lib/gcc/i486-linux-gnu/4.3.2/crtendS.o: No such file or directory
g++: /usr/lib/gcc/i486-linux-gnu/4.3.2/../../../../lib/crtn.o: No such
file or directory
</snip>
My 'uname -a' reports as 'i686', am not sure whether that could cause
this failure. Just in case if this will ring a bell for someone, this
debian box came from continuous upgrade right from 'etch'.
Thank You.
--
Senthil Kumaran S
http://www.stylesen.org/
http://www.sasenthilkumaran.com/
Re: 1.7.0-alpha1 tarballs up for testing/signing
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Senthil Kumaran S wrote on Sun, Jun 05, 2011 at 21:23:34 +0530:
> On Sun, Jun 5, 2011 at 1:53 PM, Stefan Sperling <st...@elego.de> wrote:
> > On Sun, Jun 05, 2011 at 09:18:49AM +0530, Senthil Kumaran S wrote:
> >> javahl Unable to compile. See [1] below.
> >
> > Hmmm... this fails because g++ cannot find some files it wants
> > such as /usr/lib/crti.o. Maybe you are missing a package?
> > On Debian this file seems to be in the libc6-dev package.
>
> I already have 'libc6-dev' installed in my debian box:
>
> <snip>
> $ dpkg-query -W -f='${Status} ${Version}\n' libc6-dev
> install ok installed 2.11.2-10
> </snip>
>
I have:
* Debian stable
* libc6-dev 2.11.2-10
* /usr/lib/crti.o is reported (dpkg -S) to be owned by libc6-dev
Re: 1.7.0-alpha1 tarballs up for testing/signing
Posted by Senthil Kumaran S <st...@gmail.com>.
Hi Stefan,
On Sun, Jun 5, 2011 at 1:53 PM, Stefan Sperling <st...@elego.de> wrote:
> On Sun, Jun 05, 2011 at 09:18:49AM +0530, Senthil Kumaran S wrote:
>> javahl Unable to compile. See [1] below.
>
> Hmmm... this fails because g++ cannot find some files it wants
> such as /usr/lib/crti.o. Maybe you are missing a package?
> On Debian this file seems to be in the libc6-dev package.
I already have 'libc6-dev' installed in my debian box:
<snip>
$ dpkg-query -W -f='${Status} ${Version}\n' libc6-dev
install ok installed 2.11.2-10
</snip>
>> python Unable to compile. See [2] below.
>
> This failes because Python.h is missing. You are probably missing
> the python-dev package?
After installing 'python-dev' package it worked. Thanks for pointing
it out. Following are the python binding test results:
<snip>
Ran 112 tests in 42.291s
OK
</snip>
Thank You.
--
Senthil Kumaran S
http://www.stylesen.org/
http://www.sasenthilkumaran.com/
Re: 1.7.0-alpha1 tarballs up for testing/signing
Posted by Stefan Sperling <st...@elego.de>.
On Sun, Jun 05, 2011 at 09:18:49AM +0530, Senthil Kumaran S wrote:
> javahl Unable to compile. See [1] below.
Hmmm... this fails because g++ cannot find some files it wants
such as /usr/lib/crti.o. Maybe you are missing a package?
On Debian this file seems to be in the libc6-dev package.
> python Unable to compile. See [2] below.
This failes because Python.h is missing. You are probably missing
the python-dev package?
Re: 1.7.0-alpha1 tarballs up for testing/signing
Posted by Senthil Kumaran S <st...@gmail.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hyrum K Wright wrote:
> At long request, we now have tarballs for the first 1.7.0 pre-release:
> 1.7.0-alpha1 ("phoenix-hatchling"). These were cut from trunk, and
> the magic rev is r1130808. The buildbots were green at that rev, and
> all tests pass for me locally. You can find them here:
> http://people.apache.org/~hwright/svn/1.7.0-alpha1/
Summary:
+1 to release (Unix) (though there are some problems with bindings.)
Tested:
1.7.0-alpha1 ("phoenix-hatchling") tarball with local dependencies
[ra_local, ra_svn, ra_serf, ra_neon] x [fsfs, bdb]
Dependencies:
APR 1.3.12
APR-UTIL 1.3.9
Apache httpd 2.2.15
Neon 0.29.3
Serf 0.7.2
BDB 4.7.25
OpenSSL 0.9.8o
SunJDK 1.6.0_18
SQLite 3.7.3
JUnit 3.8.2
Perl 5.10.1
Python 2.6.6
Ruby ruby 1.8.7 (2010-08-16 patchlevel 302)
Swig 1.3.40
Environment:
Debian 6.0.1 (Squeeze - recently updated)
Linux 2.6.32-5-686 #1 SMP i686 GNU/Linux
Results:
All tests PASSED!
Bindings results:
javahl Unable to compile. See [1] below.
perl All tests successful.
Files=10, Tests=214, 8 wallclock secs
( 0.07 usr 0.03 sys + 1.15 cusr 0.27 csys = 1.52 CPU)
Result: PASS
python Unable to compile. See [2] below.
ruby Finished in 626.545453 seconds.
221 tests, 3169 assertions, 0 failures, 0 errors
sha1sums (tested):
7710d703eb2365b2e91d66cedc4dbaab4ef6fbea subversion-1.7.0-alpha1.tar.bz2
212eaca54374a8e95ab5c6a15208870bbb339ae6 subversion-1.7.0-alpha1.tar.gz
Verfied sha1sums (nothing more):
e7f5456ccde81f0175eabc4af57e32f595d975e7 svn_version.h.dist
GPG Signatures:
subversion-1.7.0-alpha1.tar.bz2.asc
- -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEABECAAYFAk3q+rIACgkQ9o1G+2zNQDgglQCffMWgKNuGmlAkPQcfiFG0AVXR
posAoIZO/RnMoyMtYQPdcdYNBSp6iOo+
=78c2
- -----END PGP SIGNATURE-----
subversion-1.7.0-alpha1.tar.gz.asc
- -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEABECAAYFAk3q+r0ACgkQ9o1G+2zNQDjcawCbB+FrWy7hdP401c821FnCQ2NE
o4QAmgO6EHgVLyBIZRlAA2iTiJlVgkcS
=9GGm
- -----END PGP SIGNATURE-----
NOTE: Submitted signatures via webform too!
[1] <http://people.apache.org/~stylesen/svn-1.7.0-alpha1/javahl-compile-error.txt>
[2] <http://people.apache.org/~stylesen/svn-1.7.0-alpha1/swig-py-compile-error.txt>
Thank You.
- --
Senthil Kumaran S
http://www.stylesen.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAk3q/JUACgkQ9o1G+2zNQDhXvQCfZhUHdfBVkCZN2QP5qCzVeJat
9t0AoL1e368TlxMGQHO+sumiKLZd80XW
=7kmm
-----END PGP SIGNATURE-----
Re: 1.7.0-alpha1 tarballs up for testing/signing
Posted by Philip Martin <ph...@wandisco.com>.
Summary:
+1 to release
Platform:
Linux (Debian/stable)
Tested:
tarball + local dependencies
(local, svn, svn+sasl, serf, neon) x (fsfs, fsfs/pack/shard, bdb)
swig-pl, swig-py, swig-rb
javahl x (fsfs, bdb)
(serf/v1, neon/v2) x (fsfs, bdb)
Results:
2 tests FAIL (issue 3904, serf HTTP v1 protocol)
Local dependencies:
apache2-threaded-dev : 2.2.16-6+squeeze1
libapr1-dev : 1.4.2-6+squeeze2
libaprutil1-dev : 1.3.9+dfsg-5
libdb4.8-dev : 4.8.30-2
libneon27-dev : 0.29.3-3
libsasl2-dev : 2.1.23.dfsg1-7
libsqlite3-dev : 3.7.3-1
perl : 5.10.1-17
python2.6-dev : 2.6.6-8+b1
ruby1.8-dev : 1.8.7.302-2
openjdk-6-jdk : 6b18-1.8.7-2~squeeze1
serf : tags/0.7.2
subversion-1.7-alpha1.tar.bz2
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQEcBAABCAAGBQJN7js5AAoJEHbXiOHtGlmcNsUH/jBzTdkv6YpbJSUrT7KT1k0a
d5DVd/6vjcq886INDYnVCXJ8bRoWCEq+A+D4AaDpPcbBc80Ajeb/51DBU9Z8HD2Z
4+0DZd5osxrUgkcsL3xNa+530jhF5gOcK3o/HJgt2Egsrp0LlqOiFDz0l+3UrAZa
5t0mJWYZhqQQ0Hq4tcNBUA3YPadVee2xxBVYldIQojzwZZ+eAkv+VdKIHuxddTfJ
xHfQtO5lY2ODvoaeP7j367Nf9kIP85aQiES7Xfx/diXX79ipNOxWZTjBjMVoRfFf
wo9bBnyv/+QIct3puEbAM0eYcAMqKKO/tEm3PuO5NyhuEGY60Iq4L59aWpso74U=
=wZpj
-----END PGP SIGNATURE-----
subversion-1.7-alpha1.tar.gz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQEcBAABCAAGBQJN7jtVAAoJEHbXiOHtGlmcJ/kH/AxnAVZ2DyxnuQ+3aG/3WpV2
iKvJS1E5YvWjLpy2ttsRYqi8DFMCXZxnXtXKowJqz0S9tpBkBTh7mh/9kJYOatHD
gBg7/SfQpgyLm+MJ3ECZAlxvqKoAamEiXqIkPsKufnVXsOyWrC31+5FwK0OXVi2u
broH6xWkv2+zqdoO+gsouDX/aVAUGrPtlAugk7D7cfd/aOCPfmw3z4KfKVsEPFfJ
vNA633w6eqvXVYhWXRg/RmgirE4RndosUqMotIamNHPBWjfzHVyWSJp7w0G8etFJ
0udOsJTZnGC3gZlaMQIc0nMCbUEw7EWSoqIustk4+palppWTeBbk+o4TC8GC+eg=
=pwbO
-----END PGP SIGNATURE-----
--
Philip
Re: 1.7.0-alpha1 tarballs up for testing/signing
Posted by Philip Martin <ph...@wandisco.com>.
Paul Burba <pt...@gmail.com> writes:
>> Scratch that, the op-depth, pristine-store, and tree-conflict-data all
>> fail individually too. I hadn't realized that this:
>>
>> op-depth-test.exe 1 --fs-type bdb
>>
>> is not equivalent to this:
>>
>> op-depth-test.exe --fs-type bdb 1
>>
>> Fixed that in r1132796
>>
>> Paul
>
> In IRC Bert mentioned he saw no failures with the op-depth,
> pristine-store, and tree-conflict-data tests when using static
> libraries (he hadn't tried shared). Sure enough, if I build with
> static libraries these tests all pass.
The BDB tests pass for a shared build on my Linux machine.
--
Philip
Re: 1.7.0-alpha1 tarballs up for testing/signing
Posted by Paul Burba <pt...@gmail.com>.
On Mon, Jun 6, 2011 at 5:54 PM, Paul Burba <pt...@gmail.com> wrote:
> On Mon, Jun 6, 2011 at 2:24 PM, Paul Burba <pt...@gmail.com> wrote:
>> On Fri, Jun 3, 2011 at 3:12 PM, Hyrum K Wright <hy...@hyrumwright.org> wrote:
>>> All,
>>>
>>> At long request, we now have tarballs for the first 1.7.0 pre-release:
>>> 1.7.0-alpha1 ("phoenix-hatchling"). These were cut from trunk, and
>>> the magic rev is r1130808. The buildbots were green at that rev, and
>>> all tests pass for me locally. You can find them here:
>>> http://people.apache.org/~hwright/svn/1.7.0-alpha1/
>>>
>>> This is an alpha release, and there are obviously known issues. The
>>> purpose is to give distributors and downstream consumers a concrete
>>> milestone against which to test, as well as vet our release processes
>>> on ASF infrastructure. As you may expect, these prereleases are
>>> intended for intrepid users and testers only.
>>>
>>> As a reminder, there have been a few changes in the release artifacts
>>> since the 1.6.x series. We no longer distribute a deps tarball, but
>>> instead provide a get-deps.sh script for folks who want to fetch the
>>> dependencies. There is no longer a 'to-tigris' directory in the
>>> candidate directory. We no longer computer md5sums of the tarballs,
>>> but continue to provide sha1sums to verify integrity. (There's
>>> probably other stuff I've forgotten.)
>>>
>>> I hope to get signatures from folks by the end of Tuesday, June 7, and
>>> then do the public announcement. Historically, we've not required a
>>> full set of signatures for alphas and betas, but it would be nice to
>>> get at least some coverage besides just my own. As you send in your
>>> signature announcement, please note any issues you found with the
>>> alpha release (these will be included in the public announcement).
>>> Please send sigs here:
>>> http://work.hyrumwright.org/pub/svn/collect_sigs.py
>>>
>>> -Hyrum
>>
>> VERIFIED:
>> ---------
>> Hyrum's sig for
>> http://people.apache.org/~hwright/svn/1.7.0-alpha1/phoenix-hatchling/subversion-1.7.0-alpha1.zip
>>
>> Other than the expected differences in
>> subversion/include/svn_version.h,
>> http://people.apache.org/~hwright/svn/1.7.0-alpha1/phoenix-hatchling/subversion-1.7.0-alpha1.zip
>> is the same as https://svn.apache.org/repos/asf/subversion/trunk@1130808.
>>
>> BUILD FAILURES:
>> --------------
>> I was able to build the __JAVAHL__ target, but the tests
>> (__JAVAHL_TESTS__) fail to build, see attached log. I was able to
>> build the tests with trunk@1132646, so whatever is causing this
>> failure has been fixed.
>>
>>
>> TESTED:
>> -------
>> [Release-Build] x[ fsfs | bdb ] x [ file | svn | http (neon) | http (serf) ]
>> Ruby bindings
>>
>> RESULTS:
>> --------
>> Ruby bindings: Pass
>>
>> ----------------------------------------
>>
>> All op-depth-test.exe tests fail when bdb is the backend. All the
>> failures are similar to this:
>>
>> [[[
>> C:\SVN\src-trunk\Release\subversion\tests\libsvn_wc>op-depth-test.exe
>> --fs-type bdb
>> svn_tests: E180001: Unable to connect to a repository at URL
>> 'file:///C:/SVN/src-trunk/Release/subversion/tests/libsvn_wc/svn-test-work/repositories/wc_wc_copies'
>> svn_tests: E180001: Unable to open an ra_local session to URL
>> svn_tests: E180001: Unable to open repository
>> 'file:///C:/SVN/src-trunk/Release/subversion/tests/libsvn_wc/svn-test-work/repositories/wc_wc_copies'
>> svn_tests: E160029: Berkeley DB error for filesystem
>> 'C:/SVN/src-trunk/Release/subversion/tests/libsvn_wc/svn-test-work/repositories/wc_wc_copies/db'
>> while opening environment:
>>
>> svn_tests: E160029: Operation not permitted
>> svn_tests: E000000: bdb: DB_REGISTER limits processes to one open
>> DB_ENV handle per environment
>> FAIL: op-depth-test.exe 1: test_wc_wc_copies
>> ]]]
>>
>> If run individually, each test passes.
>>
>> ----------------------------------------
>>
>> Two pristine-store tests fail with a segfault whenever bdb is the backend:
>>
>> FAIL: pristine-store-test.exe 1: pristine_write_read
>> FAIL: pristine-store-test.exe 2: pristine_delete_while_open
>>
>> The problem looks similar to that with op-depth-tests.exe, and again
>> the test pass if run individually:
>>
>> [[[
>> C:\SVN\src-trunk-2\Debug\subversion\tests\libsvn_wc>pristine-store-test.exe
>> --fs-type bdb
>> ..\..\..\subversion\tests\libsvn_wc\pristine-store-test.c:122: (apr_err=180001)
>> ..\..\..\subversion\tests\libsvn_wc\pristine-store-test.c:66: (apr_err=180001)
>> ..\..\..\subversion\tests\libsvn_wc\utils.c:143: (apr_err=180001)
>> ..\..\..\subversion\tests\libsvn_wc\utils.c:85: (apr_err=180001)
>> ..\..\..\subversion\libsvn_client\checkout.c:138: (apr_err=180001)
>> ..\..\..\subversion\libsvn_client\ra.c:464: (apr_err=180001)
>> ..\..\..\subversion\libsvn_client\ra.c:324: (apr_err=180001)
>> ..\..\..\subversion\libsvn_ra\ra_loader.c:496: (apr_err=180001)
>> ..\..\..\subversion\libsvn_ra\ra_loader.c:496: (apr_err=180001)
>> svn_tests: E180001: Unable to connect to a repository at URL
>> 'file:///C:/SVN/src-trunk-2/Debug/subversion/tests/libsvn_wc/svn-test-work/repositories/pristine_wr
>> ite_read'
>> ..\..\..\subversion\libsvn_ra_local\ra_plugin.c:475: (apr_err=180001)
>> ..\..\..\subversion\libsvn_ra_local\ra_plugin.c:475: (apr_err=180001)
>> svn_tests: E180001: Unable to open an ra_local session to URL
>> ..\..\..\subversion\libsvn_ra_local\split_url.c:54: (apr_err=180001)
>> svn_tests: E180001: Unable to open repository
>> 'file:///C:/SVN/src-trunk-2/Debug/subversion/tests/libsvn_wc/svn-test-work/repositories/pristine_write_read'
>> ..\..\..\subversion\libsvn_repos\repos.c:1374: (apr_err=160029)
>> ..\..\..\subversion\libsvn_fs\fs-loader.c:436: (apr_err=160029)
>> ..\..\..\subversion\libsvn_fs_base\fs.c:542: (apr_err=160029)
>> svn_tests: E160029: Berkeley DB error for filesystem
>> 'C:/SVN/src-trunk-2/Debug/subversion/tests/libsvn_wc/svn-test-work/repositories/pristine_write_read/db'
>> whi
>> le opening environment:
>>
>> ..\..\..\subversion\libsvn_fs_base\bdb\env.c:710: (apr_err=160029)
>> ..\..\..\subversion\libsvn_fs_base\bdb\env.c:588: (apr_err=160029)
>> ..\..\..\subversion\libsvn_fs_base\bdb\bdb-err.c:62: (apr_err=160029)
>> svn_tests: E160029: Operation not permitted
>> ..\..\..\subversion\libsvn_fs_base\bdb\env.c:229: (apr_err=0)
>> svn_tests: E000000: bdb: DB_REGISTER limits processes to one open
>> DB_ENV handle per environment
>> ]]]
>> ----------------------------------------
>>
>> One tree-conflict-data tests fails with a segfault whenever bdb is the backend:
>>
>> FAIL: tree-conflict-data-test.exe 3: read and write tree conflicts
>>
>> The problem looks similar to that with op-depth-tests.exe, and again
>> the test passes if run individually:
>
> Scratch that, the op-depth, pristine-store, and tree-conflict-data all
> fail individually too. I hadn't realized that this:
>
> op-depth-test.exe 1 --fs-type bdb
>
> is not equivalent to this:
>
> op-depth-test.exe --fs-type bdb 1
>
> Fixed that in r1132796
>
> Paul
In IRC Bert mentioned he saw no failures with the op-depth,
pristine-store, and tree-conflict-data tests when using static
libraries (he hadn't tried shared). Sure enough, if I build with
static libraries these tests all pass.
Given that "This is an alpha release, and there are obviously known
issues" I'm voting +1 for release (with the understanding that the
aforementioned failures are among the "know issues").
Here's my sig for
http://people.apache.org/~hwright/svn/1.7.0-alpha1/phoenix-hatchling/subversion-1.7.0-alpha1.zip
(submitted it to collect_sigs.py too):
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
iD8DBQBN7jeh2RaJMFP83FURArfiAJ9ZXrfef7QTs5MZu7MLx0+QMbk/dQCfeUNM
wFi9DWwEn0r9ldfsr4HKSY4=
=YrS3
-----END PGP SIGNATURE-----
Paul
Re: 1.7.0-alpha1 tarballs up for testing/signing
Posted by Paul Burba <pt...@gmail.com>.
On Mon, Jun 6, 2011 at 2:24 PM, Paul Burba <pt...@gmail.com> wrote:
> On Fri, Jun 3, 2011 at 3:12 PM, Hyrum K Wright <hy...@hyrumwright.org> wrote:
>> All,
>>
>> At long request, we now have tarballs for the first 1.7.0 pre-release:
>> 1.7.0-alpha1 ("phoenix-hatchling"). These were cut from trunk, and
>> the magic rev is r1130808. The buildbots were green at that rev, and
>> all tests pass for me locally. You can find them here:
>> http://people.apache.org/~hwright/svn/1.7.0-alpha1/
>>
>> This is an alpha release, and there are obviously known issues. The
>> purpose is to give distributors and downstream consumers a concrete
>> milestone against which to test, as well as vet our release processes
>> on ASF infrastructure. As you may expect, these prereleases are
>> intended for intrepid users and testers only.
>>
>> As a reminder, there have been a few changes in the release artifacts
>> since the 1.6.x series. We no longer distribute a deps tarball, but
>> instead provide a get-deps.sh script for folks who want to fetch the
>> dependencies. There is no longer a 'to-tigris' directory in the
>> candidate directory. We no longer computer md5sums of the tarballs,
>> but continue to provide sha1sums to verify integrity. (There's
>> probably other stuff I've forgotten.)
>>
>> I hope to get signatures from folks by the end of Tuesday, June 7, and
>> then do the public announcement. Historically, we've not required a
>> full set of signatures for alphas and betas, but it would be nice to
>> get at least some coverage besides just my own. As you send in your
>> signature announcement, please note any issues you found with the
>> alpha release (these will be included in the public announcement).
>> Please send sigs here:
>> http://work.hyrumwright.org/pub/svn/collect_sigs.py
>>
>> -Hyrum
>
> VERIFIED:
> ---------
> Hyrum's sig for
> http://people.apache.org/~hwright/svn/1.7.0-alpha1/phoenix-hatchling/subversion-1.7.0-alpha1.zip
>
> Other than the expected differences in
> subversion/include/svn_version.h,
> http://people.apache.org/~hwright/svn/1.7.0-alpha1/phoenix-hatchling/subversion-1.7.0-alpha1.zip
> is the same as https://svn.apache.org/repos/asf/subversion/trunk@1130808.
>
> BUILD FAILURES:
> --------------
> I was able to build the __JAVAHL__ target, but the tests
> (__JAVAHL_TESTS__) fail to build, see attached log. I was able to
> build the tests with trunk@1132646, so whatever is causing this
> failure has been fixed.
>
>
> TESTED:
> -------
> [Release-Build] x[ fsfs | bdb ] x [ file | svn | http (neon) | http (serf) ]
> Ruby bindings
>
> RESULTS:
> --------
> Ruby bindings: Pass
>
> ----------------------------------------
>
> All op-depth-test.exe tests fail when bdb is the backend. All the
> failures are similar to this:
>
> [[[
> C:\SVN\src-trunk\Release\subversion\tests\libsvn_wc>op-depth-test.exe
> --fs-type bdb
> svn_tests: E180001: Unable to connect to a repository at URL
> 'file:///C:/SVN/src-trunk/Release/subversion/tests/libsvn_wc/svn-test-work/repositories/wc_wc_copies'
> svn_tests: E180001: Unable to open an ra_local session to URL
> svn_tests: E180001: Unable to open repository
> 'file:///C:/SVN/src-trunk/Release/subversion/tests/libsvn_wc/svn-test-work/repositories/wc_wc_copies'
> svn_tests: E160029: Berkeley DB error for filesystem
> 'C:/SVN/src-trunk/Release/subversion/tests/libsvn_wc/svn-test-work/repositories/wc_wc_copies/db'
> while opening environment:
>
> svn_tests: E160029: Operation not permitted
> svn_tests: E000000: bdb: DB_REGISTER limits processes to one open
> DB_ENV handle per environment
> FAIL: op-depth-test.exe 1: test_wc_wc_copies
> ]]]
>
> If run individually, each test passes.
>
> ----------------------------------------
>
> Two pristine-store tests fail with a segfault whenever bdb is the backend:
>
> FAIL: pristine-store-test.exe 1: pristine_write_read
> FAIL: pristine-store-test.exe 2: pristine_delete_while_open
>
> The problem looks similar to that with op-depth-tests.exe, and again
> the test pass if run individually:
>
> [[[
> C:\SVN\src-trunk-2\Debug\subversion\tests\libsvn_wc>pristine-store-test.exe
> --fs-type bdb
> ..\..\..\subversion\tests\libsvn_wc\pristine-store-test.c:122: (apr_err=180001)
> ..\..\..\subversion\tests\libsvn_wc\pristine-store-test.c:66: (apr_err=180001)
> ..\..\..\subversion\tests\libsvn_wc\utils.c:143: (apr_err=180001)
> ..\..\..\subversion\tests\libsvn_wc\utils.c:85: (apr_err=180001)
> ..\..\..\subversion\libsvn_client\checkout.c:138: (apr_err=180001)
> ..\..\..\subversion\libsvn_client\ra.c:464: (apr_err=180001)
> ..\..\..\subversion\libsvn_client\ra.c:324: (apr_err=180001)
> ..\..\..\subversion\libsvn_ra\ra_loader.c:496: (apr_err=180001)
> ..\..\..\subversion\libsvn_ra\ra_loader.c:496: (apr_err=180001)
> svn_tests: E180001: Unable to connect to a repository at URL
> 'file:///C:/SVN/src-trunk-2/Debug/subversion/tests/libsvn_wc/svn-test-work/repositories/pristine_wr
> ite_read'
> ..\..\..\subversion\libsvn_ra_local\ra_plugin.c:475: (apr_err=180001)
> ..\..\..\subversion\libsvn_ra_local\ra_plugin.c:475: (apr_err=180001)
> svn_tests: E180001: Unable to open an ra_local session to URL
> ..\..\..\subversion\libsvn_ra_local\split_url.c:54: (apr_err=180001)
> svn_tests: E180001: Unable to open repository
> 'file:///C:/SVN/src-trunk-2/Debug/subversion/tests/libsvn_wc/svn-test-work/repositories/pristine_write_read'
> ..\..\..\subversion\libsvn_repos\repos.c:1374: (apr_err=160029)
> ..\..\..\subversion\libsvn_fs\fs-loader.c:436: (apr_err=160029)
> ..\..\..\subversion\libsvn_fs_base\fs.c:542: (apr_err=160029)
> svn_tests: E160029: Berkeley DB error for filesystem
> 'C:/SVN/src-trunk-2/Debug/subversion/tests/libsvn_wc/svn-test-work/repositories/pristine_write_read/db'
> whi
> le opening environment:
>
> ..\..\..\subversion\libsvn_fs_base\bdb\env.c:710: (apr_err=160029)
> ..\..\..\subversion\libsvn_fs_base\bdb\env.c:588: (apr_err=160029)
> ..\..\..\subversion\libsvn_fs_base\bdb\bdb-err.c:62: (apr_err=160029)
> svn_tests: E160029: Operation not permitted
> ..\..\..\subversion\libsvn_fs_base\bdb\env.c:229: (apr_err=0)
> svn_tests: E000000: bdb: DB_REGISTER limits processes to one open
> DB_ENV handle per environment
> ]]]
> ----------------------------------------
>
> One tree-conflict-data tests fails with a segfault whenever bdb is the backend:
>
> FAIL: tree-conflict-data-test.exe 3: read and write tree conflicts
>
> The problem looks similar to that with op-depth-tests.exe, and again
> the test passes if run individually:
Scratch that, the op-depth, pristine-store, and tree-conflict-data all
fail individually too. I hadn't realized that this:
op-depth-test.exe 1 --fs-type bdb
is not equivalent to this:
op-depth-test.exe --fs-type bdb 1
Fixed that in r1132796
Paul
Re: 1.7.0-alpha1 tarballs up for testing/signing
Posted by Paul Burba <pt...@gmail.com>.
On Mon, Jun 6, 2011 at 2:24 PM, Paul Burba <pt...@gmail.com> wrote:
> On Fri, Jun 3, 2011 at 3:12 PM, Hyrum K Wright <hy...@hyrumwright.org> wrote:
>> All,
>>
>> At long request, we now have tarballs for the first 1.7.0 pre-release:
>> 1.7.0-alpha1 ("phoenix-hatchling"). These were cut from trunk, and
>> the magic rev is r1130808. The buildbots were green at that rev, and
>> all tests pass for me locally. You can find them here:
>> http://people.apache.org/~hwright/svn/1.7.0-alpha1/
>>
>> This is an alpha release, and there are obviously known issues. The
>> purpose is to give distributors and downstream consumers a concrete
>> milestone against which to test, as well as vet our release processes
>> on ASF infrastructure. As you may expect, these prereleases are
>> intended for intrepid users and testers only.
>>
>> As a reminder, there have been a few changes in the release artifacts
>> since the 1.6.x series. We no longer distribute a deps tarball, but
>> instead provide a get-deps.sh script for folks who want to fetch the
>> dependencies. There is no longer a 'to-tigris' directory in the
>> candidate directory. We no longer computer md5sums of the tarballs,
>> but continue to provide sha1sums to verify integrity. (There's
>> probably other stuff I've forgotten.)
>>
>> I hope to get signatures from folks by the end of Tuesday, June 7, and
>> then do the public announcement. Historically, we've not required a
>> full set of signatures for alphas and betas, but it would be nice to
>> get at least some coverage besides just my own. As you send in your
>> signature announcement, please note any issues you found with the
>> alpha release (these will be included in the public announcement).
>> Please send sigs here:
>> http://work.hyrumwright.org/pub/svn/collect_sigs.py
>>
>> -Hyrum
<SNIP>
> Two redirect tests fail over all 4 DAV combinations:
>
> FAIL: redirect_tests.py 2: redirected checkout
> FAIL: redirect_tests.py 3: redirected update
>
> The redirect the failures are similar to this:
>
> [[[
> C:\SVN\src-trunk>win-tests.py -r -c -u http://localhost --http-library
> neon --fs-type fsfs --test=redirect#2 --log-to-stdout
> Testing Release configuration on remote repository http://localhost.
> START: redirect_tests.py
> CMD: svnadmin.exe create svn-test-work\local_tmp\repos
> --bdb-txn-nosync --fs-type=fsfs
> <TIME = 0.033000>
> CMD: svn.exe import -m "Log message for revision 1."
> svn-test-work\local_tmp\greekfiles
> http://localhost/svn-test-work/local_tmp/repos --config-dir
> C:\SVN\src-t
> runk\Release\subversion\tests\cmdline\svn-test-work\local_tmp\config
> --password rayjandom --no-auth-cache --username jrandom
> <TIME = 0.209000>
> Adding svn-test-work\local_tmp\greekfiles\A
> Adding svn-test-work\local_tmp\greekfiles\A\B
> Adding svn-test-work\local_tmp\greekfiles\A\B\lambda
> Adding svn-test-work\local_tmp\greekfiles\A\B\E
> Adding svn-test-work\local_tmp\greekfiles\A\B\E\alpha
> Adding svn-test-work\local_tmp\greekfiles\A\B\E\beta
> Adding svn-test-work\local_tmp\greekfiles\A\B\F
> Adding svn-test-work\local_tmp\greekfiles\A\mu
> Adding svn-test-work\local_tmp\greekfiles\A\C
> Adding svn-test-work\local_tmp\greekfiles\A\D
> Adding svn-test-work\local_tmp\greekfiles\A\D\gamma
> Adding svn-test-work\local_tmp\greekfiles\A\D\G
> Adding svn-test-work\local_tmp\greekfiles\A\D\G\pi
> Adding svn-test-work\local_tmp\greekfiles\A\D\G\rho
> Adding svn-test-work\local_tmp\greekfiles\A\D\G\tau
> Adding svn-test-work\local_tmp\greekfiles\A\D\H
> Adding svn-test-work\local_tmp\greekfiles\A\D\H\chi
> Adding svn-test-work\local_tmp\greekfiles\A\D\H\omega
> Adding svn-test-work\local_tmp\greekfiles\A\D\H\psi
> Adding svn-test-work\local_tmp\greekfiles\iota
>
> Committed revision 1.
> CMD: svnadmin.exe create svn-test-work\repositories\redirect_tests-2
> --bdb-txn-nosync --fs-type=fsfs
> <TIME = 0.035000>
> CMD: svnadmin.exe dump svn-test-work\local_tmp\repos | svnadmin.exe
> load svn-test-work\repositories\redirect_tests-2 --ignore-uuid
> <TIME = 0.002000>
> CMD: svn.exe co
> http://localhost/svn-test-work/repositories/REDIRECT-PERM-redirect_tests-2
> svn-test-work\working_copies\redirect_tests-2.my --config-dir C:\SVN\
> src-trunk\Release\subversion\tests\cmdline\svn-test-work\local_tmp\config
> --password rayjandom --no-auth-cache --username jrandom
> CMD: C:\SVN\src-trunk\Release\subversion\svn\svn.exe co
> http://localhost/svn-test-work/repositories/REDIRECT-PERM-redirect_tests-2
> svn-test-work\working_copies\
> redirect_tests-2.my --config-dir
> C:\SVN\src-trunk\Release\subversion\tests\cmdline\svn-test-work\local_tmp\config
> --password rayjandom --no-auth-cache --usernam
> e jrandom exited with 1
> <TIME = 0.034000>
> svn: E720003: Unable to connect to a repository at URL
> 'http://localhost/svn-test-work/repositories/REDIRECT-PERM-redirect_tests-2'
> svn: E720003: Could not open the requested SVN filesystem
> Traceback (most recent call last):
> File "C:\SVN\src-trunk\subversion\tests\cmdline\svntest\main.py",
> line 1288, in run
> rc = self.pred.run(sandbox)
> File "C:\SVN\src-trunk\subversion\tests\cmdline\svntest\testcase.py",
> line 254, in run
> return self._delegate.run(sandbox)
> File "C:\SVN\src-trunk\subversion\tests\cmdline\svntest\testcase.py",
> line 176, in run
> return self.func(sandbox)
> File "C:\SVN\src-trunk\subversion\tests\cmdline\redirect_tests.py",
> line 102, in redirected_checkout
> exit_code, out, err = svntest.main.run_svn(None, 'co', co_url, wc_dir)
> File "C:\SVN\src-trunk\subversion\tests\cmdline\svntest\main.py",
> line 591, in run_svn
> *(_with_auth(_with_config_dir(varargs))))
> File "C:\SVN\src-trunk\subversion\tests\cmdline\svntest\main.py",
> line 347, in run_command
> None, *varargs)
> File "C:\SVN\src-trunk\subversion\tests\cmdline\svntest\main.py",
> line 523, in run_command_stdin
> raise Failure
> Failure
> FAIL: redirect_tests.py 2: redirected checkout
> END: redirect_tests.py
> ELAPSED: redirect_tests.py 0:00:00.584000
> ]]]
Disregard the redirect failures. Those were due to the fact I used my
own httpd.conf file rather than letting win-tests.py create it (thanks
rhuijben)
Paul
Re: 1.7.0-alpha1 tarballs up for testing/signing
Posted by Paul Burba <pt...@gmail.com>.
On Fri, Jun 3, 2011 at 3:12 PM, Hyrum K Wright <hy...@hyrumwright.org> wrote:
> All,
>
> At long request, we now have tarballs for the first 1.7.0 pre-release:
> 1.7.0-alpha1 ("phoenix-hatchling"). These were cut from trunk, and
> the magic rev is r1130808. The buildbots were green at that rev, and
> all tests pass for me locally. You can find them here:
> http://people.apache.org/~hwright/svn/1.7.0-alpha1/
>
> This is an alpha release, and there are obviously known issues. The
> purpose is to give distributors and downstream consumers a concrete
> milestone against which to test, as well as vet our release processes
> on ASF infrastructure. As you may expect, these prereleases are
> intended for intrepid users and testers only.
>
> As a reminder, there have been a few changes in the release artifacts
> since the 1.6.x series. We no longer distribute a deps tarball, but
> instead provide a get-deps.sh script for folks who want to fetch the
> dependencies. There is no longer a 'to-tigris' directory in the
> candidate directory. We no longer computer md5sums of the tarballs,
> but continue to provide sha1sums to verify integrity. (There's
> probably other stuff I've forgotten.)
>
> I hope to get signatures from folks by the end of Tuesday, June 7, and
> then do the public announcement. Historically, we've not required a
> full set of signatures for alphas and betas, but it would be nice to
> get at least some coverage besides just my own. As you send in your
> signature announcement, please note any issues you found with the
> alpha release (these will be included in the public announcement).
> Please send sigs here:
> http://work.hyrumwright.org/pub/svn/collect_sigs.py
>
> -Hyrum
VERIFIED:
---------
Hyrum's sig for
http://people.apache.org/~hwright/svn/1.7.0-alpha1/phoenix-hatchling/subversion-1.7.0-alpha1.zip
Other than the expected differences in
subversion/include/svn_version.h,
http://people.apache.org/~hwright/svn/1.7.0-alpha1/phoenix-hatchling/subversion-1.7.0-alpha1.zip
is the same as https://svn.apache.org/repos/asf/subversion/trunk@1130808.
BUILD FAILURES:
--------------
I was able to build the __JAVAHL__ target, but the tests
(__JAVAHL_TESTS__) fail to build, see attached log. I was able to
build the tests with trunk@1132646, so whatever is causing this
failure has been fixed.
TESTED:
-------
[Release-Build] x[ fsfs | bdb ] x [ file | svn | http (neon) | http (serf) ]
Ruby bindings
RESULTS:
--------
Ruby bindings: Pass
----------------------------------------
All op-depth-test.exe tests fail when bdb is the backend. All the
failures are similar to this:
[[[
C:\SVN\src-trunk\Release\subversion\tests\libsvn_wc>op-depth-test.exe
--fs-type bdb
svn_tests: E180001: Unable to connect to a repository at URL
'file:///C:/SVN/src-trunk/Release/subversion/tests/libsvn_wc/svn-test-work/repositories/wc_wc_copies'
svn_tests: E180001: Unable to open an ra_local session to URL
svn_tests: E180001: Unable to open repository
'file:///C:/SVN/src-trunk/Release/subversion/tests/libsvn_wc/svn-test-work/repositories/wc_wc_copies'
svn_tests: E160029: Berkeley DB error for filesystem
'C:/SVN/src-trunk/Release/subversion/tests/libsvn_wc/svn-test-work/repositories/wc_wc_copies/db'
while opening environment:
svn_tests: E160029: Operation not permitted
svn_tests: E000000: bdb: DB_REGISTER limits processes to one open
DB_ENV handle per environment
FAIL: op-depth-test.exe 1: test_wc_wc_copies
]]]
If run individually, each test passes.
----------------------------------------
Two pristine-store tests fail with a segfault whenever bdb is the backend:
FAIL: pristine-store-test.exe 1: pristine_write_read
FAIL: pristine-store-test.exe 2: pristine_delete_while_open
The problem looks similar to that with op-depth-tests.exe, and again
the test pass if run individually:
[[[
C:\SVN\src-trunk-2\Debug\subversion\tests\libsvn_wc>pristine-store-test.exe
--fs-type bdb
..\..\..\subversion\tests\libsvn_wc\pristine-store-test.c:122: (apr_err=180001)
..\..\..\subversion\tests\libsvn_wc\pristine-store-test.c:66: (apr_err=180001)
..\..\..\subversion\tests\libsvn_wc\utils.c:143: (apr_err=180001)
..\..\..\subversion\tests\libsvn_wc\utils.c:85: (apr_err=180001)
..\..\..\subversion\libsvn_client\checkout.c:138: (apr_err=180001)
..\..\..\subversion\libsvn_client\ra.c:464: (apr_err=180001)
..\..\..\subversion\libsvn_client\ra.c:324: (apr_err=180001)
..\..\..\subversion\libsvn_ra\ra_loader.c:496: (apr_err=180001)
..\..\..\subversion\libsvn_ra\ra_loader.c:496: (apr_err=180001)
svn_tests: E180001: Unable to connect to a repository at URL
'file:///C:/SVN/src-trunk-2/Debug/subversion/tests/libsvn_wc/svn-test-work/repositories/pristine_wr
ite_read'
..\..\..\subversion\libsvn_ra_local\ra_plugin.c:475: (apr_err=180001)
..\..\..\subversion\libsvn_ra_local\ra_plugin.c:475: (apr_err=180001)
svn_tests: E180001: Unable to open an ra_local session to URL
..\..\..\subversion\libsvn_ra_local\split_url.c:54: (apr_err=180001)
svn_tests: E180001: Unable to open repository
'file:///C:/SVN/src-trunk-2/Debug/subversion/tests/libsvn_wc/svn-test-work/repositories/pristine_write_read'
..\..\..\subversion\libsvn_repos\repos.c:1374: (apr_err=160029)
..\..\..\subversion\libsvn_fs\fs-loader.c:436: (apr_err=160029)
..\..\..\subversion\libsvn_fs_base\fs.c:542: (apr_err=160029)
svn_tests: E160029: Berkeley DB error for filesystem
'C:/SVN/src-trunk-2/Debug/subversion/tests/libsvn_wc/svn-test-work/repositories/pristine_write_read/db'
whi
le opening environment:
..\..\..\subversion\libsvn_fs_base\bdb\env.c:710: (apr_err=160029)
..\..\..\subversion\libsvn_fs_base\bdb\env.c:588: (apr_err=160029)
..\..\..\subversion\libsvn_fs_base\bdb\bdb-err.c:62: (apr_err=160029)
svn_tests: E160029: Operation not permitted
..\..\..\subversion\libsvn_fs_base\bdb\env.c:229: (apr_err=0)
svn_tests: E000000: bdb: DB_REGISTER limits processes to one open
DB_ENV handle per environment
]]]
----------------------------------------
One tree-conflict-data tests fails with a segfault whenever bdb is the backend:
FAIL: tree-conflict-data-test.exe 3: read and write tree conflicts
The problem looks similar to that with op-depth-tests.exe, and again
the test passes if run individually:
[[[
C:\SVN\src-trunk\Debug\subversion\tests\libsvn_wc>tree-conflict-data-test.exe
--fs-type bdb
PASS: tree-conflict-data-test.exe 1: deserialize tree conflict
PASS: tree-conflict-data-test.exe 2: serialize tree conflict
..\..\..\subversion\tests\libsvn_wc\tree-conflict-data-test.c:199:
(apr_err=180001)
..\..\..\subversion\tests\libsvn_wc\utils.c:143: (apr_err=180001)
..\..\..\subversion\tests\libsvn_wc\utils.c:85: (apr_err=180001)
..\..\..\subversion\libsvn_client\checkout.c:138: (apr_err=180001)
..\..\..\subversion\libsvn_client\ra.c:464: (apr_err=180001)
..\..\..\subversion\libsvn_client\ra.c:324: (apr_err=180001)
..\..\..\subversion\libsvn_ra\ra_loader.c:496: (apr_err=180001)
..\..\..\subversion\libsvn_ra\ra_loader.c:496: (apr_err=180001)
svn_tests: E180001: Unable to connect to a repository at URL
'file:///C:/SVN/src-trunk/Debug/subversion/tests/libsvn_wc/svn-test-work/repositories/read_write_tr
ee_conflicts'
..\..\..\subversion\libsvn_ra_local\ra_plugin.c:475: (apr_err=180001)
..\..\..\subversion\libsvn_ra_local\ra_plugin.c:475: (apr_err=180001)
svn_tests: E180001: Unable to open an ra_local session to URL
..\..\..\subversion\libsvn_ra_local\split_url.c:54: (apr_err=180001)
svn_tests: E180001: Unable to open repository
'file:///C:/SVN/src-trunk/Debug/subversion/tests/libsvn_wc/svn-test-work/repositories/read_write_tree_conflicts'
..\..\..\subversion\libsvn_repos\repos.c:1374: (apr_err=160029)
..\..\..\subversion\libsvn_fs\fs-loader.c:436: (apr_err=160029)
..\..\..\subversion\libsvn_fs_base\fs.c:542: (apr_err=160029)
svn_tests: E160029: Berkeley DB error for filesystem
'C:/SVN/src-trunk/Debug/subversion/tests/libsvn_wc/svn-test-work/repositories/read_write_tree_conflicts/db'
while opening environment:
..\..\..\subversion\libsvn_fs_base\bdb\env.c:710: (apr_err=160029)
..\..\..\subversion\libsvn_fs_base\bdb\env.c:588: (apr_err=160029)
..\..\..\subversion\libsvn_fs_base\bdb\bdb-err.c:62: (apr_err=160029)
svn_tests: E160029: Operation not permitted
..\..\..\subversion\libsvn_fs_base\bdb\env.c:229: (apr_err=0)
svn_tests: E000000: bdb: DB_REGISTER limits processes to one open
DB_ENV handle per environment
]]]
----------------------------------------
Two redirect tests fail over all 4 DAV combinations:
FAIL: redirect_tests.py 2: redirected checkout
FAIL: redirect_tests.py 3: redirected update
The redirect the failures are similar to this:
[[[
C:\SVN\src-trunk>win-tests.py -r -c -u http://localhost --http-library
neon --fs-type fsfs --test=redirect#2 --log-to-stdout
Testing Release configuration on remote repository http://localhost.
START: redirect_tests.py
CMD: svnadmin.exe create svn-test-work\local_tmp\repos
--bdb-txn-nosync --fs-type=fsfs
<TIME = 0.033000>
CMD: svn.exe import -m "Log message for revision 1."
svn-test-work\local_tmp\greekfiles
http://localhost/svn-test-work/local_tmp/repos --config-dir
C:\SVN\src-t
runk\Release\subversion\tests\cmdline\svn-test-work\local_tmp\config
--password rayjandom --no-auth-cache --username jrandom
<TIME = 0.209000>
Adding svn-test-work\local_tmp\greekfiles\A
Adding svn-test-work\local_tmp\greekfiles\A\B
Adding svn-test-work\local_tmp\greekfiles\A\B\lambda
Adding svn-test-work\local_tmp\greekfiles\A\B\E
Adding svn-test-work\local_tmp\greekfiles\A\B\E\alpha
Adding svn-test-work\local_tmp\greekfiles\A\B\E\beta
Adding svn-test-work\local_tmp\greekfiles\A\B\F
Adding svn-test-work\local_tmp\greekfiles\A\mu
Adding svn-test-work\local_tmp\greekfiles\A\C
Adding svn-test-work\local_tmp\greekfiles\A\D
Adding svn-test-work\local_tmp\greekfiles\A\D\gamma
Adding svn-test-work\local_tmp\greekfiles\A\D\G
Adding svn-test-work\local_tmp\greekfiles\A\D\G\pi
Adding svn-test-work\local_tmp\greekfiles\A\D\G\rho
Adding svn-test-work\local_tmp\greekfiles\A\D\G\tau
Adding svn-test-work\local_tmp\greekfiles\A\D\H
Adding svn-test-work\local_tmp\greekfiles\A\D\H\chi
Adding svn-test-work\local_tmp\greekfiles\A\D\H\omega
Adding svn-test-work\local_tmp\greekfiles\A\D\H\psi
Adding svn-test-work\local_tmp\greekfiles\iota
Committed revision 1.
CMD: svnadmin.exe create svn-test-work\repositories\redirect_tests-2
--bdb-txn-nosync --fs-type=fsfs
<TIME = 0.035000>
CMD: svnadmin.exe dump svn-test-work\local_tmp\repos | svnadmin.exe
load svn-test-work\repositories\redirect_tests-2 --ignore-uuid
<TIME = 0.002000>
CMD: svn.exe co
http://localhost/svn-test-work/repositories/REDIRECT-PERM-redirect_tests-2
svn-test-work\working_copies\redirect_tests-2.my --config-dir C:\SVN\
src-trunk\Release\subversion\tests\cmdline\svn-test-work\local_tmp\config
--password rayjandom --no-auth-cache --username jrandom
CMD: C:\SVN\src-trunk\Release\subversion\svn\svn.exe co
http://localhost/svn-test-work/repositories/REDIRECT-PERM-redirect_tests-2
svn-test-work\working_copies\
redirect_tests-2.my --config-dir
C:\SVN\src-trunk\Release\subversion\tests\cmdline\svn-test-work\local_tmp\config
--password rayjandom --no-auth-cache --usernam
e jrandom exited with 1
<TIME = 0.034000>
svn: E720003: Unable to connect to a repository at URL
'http://localhost/svn-test-work/repositories/REDIRECT-PERM-redirect_tests-2'
svn: E720003: Could not open the requested SVN filesystem
Traceback (most recent call last):
File "C:\SVN\src-trunk\subversion\tests\cmdline\svntest\main.py",
line 1288, in run
rc = self.pred.run(sandbox)
File "C:\SVN\src-trunk\subversion\tests\cmdline\svntest\testcase.py",
line 254, in run
return self._delegate.run(sandbox)
File "C:\SVN\src-trunk\subversion\tests\cmdline\svntest\testcase.py",
line 176, in run
return self.func(sandbox)
File "C:\SVN\src-trunk\subversion\tests\cmdline\redirect_tests.py",
line 102, in redirected_checkout
exit_code, out, err = svntest.main.run_svn(None, 'co', co_url, wc_dir)
File "C:\SVN\src-trunk\subversion\tests\cmdline\svntest\main.py",
line 591, in run_svn
*(_with_auth(_with_config_dir(varargs))))
File "C:\SVN\src-trunk\subversion\tests\cmdline\svntest\main.py",
line 347, in run_command
None, *varargs)
File "C:\SVN\src-trunk\subversion\tests\cmdline\svntest\main.py",
line 523, in run_command_stdin
raise Failure
Failure
FAIL: redirect_tests.py 2: redirected checkout
END: redirect_tests.py
ELAPSED: redirect_tests.py 0:00:00.584000
]]]
Looking into these failures.
PLATFORM:
---------
MS Windows 7 Home Premium 6.1.7600 Build 7600
Intel Core i7 M 620 2.67GHz 4 GB RAM
Microsoft Visual Studio 2008 Version 9.0.30729.1 SP
DEPENDENCIES:
-------------
APR: 1.4.5
APR-UTIL: 1.3.12
Neon: 0.29.5
zlib: 1.2.4
OpenSSL: 0.9.8q
Apache: 2.2.19
BDB: 4.8.30
sqlite: 3.7.3
Python: 2.6.6 (ActivePython 2.6.6.17)
Perl: 5.10.1
Ruby: ruby 1.8.7
java: 1.6.0_21
junit: 4.8.2
swig: 1.3.40
serf: 0.7.2
Paul
Re: 1.7.0-alpha1 tarballs up for testing/signing
Posted by Stefan Sperling <st...@elego.de>.
On Fri, Jun 03, 2011 at 02:12:07PM -0500, Hyrum K Wright wrote:
> All,
>
> At long request, we now have tarballs for the first 1.7.0 pre-release:
> 1.7.0-alpha1 ("phoenix-hatchling"). These were cut from trunk, and
> the magic rev is r1130808. The buildbots were green at that rev, and
> all tests pass for me locally. You can find them here:
> http://people.apache.org/~hwright/svn/1.7.0-alpha1/
Summary: +1 to release
Tested: [bdb | fsfs] x [ra_local | ra_svn | ra_neon | ra_serf]
swig bindings
Test results: All passed.
Platform: OpenBSD 4.9 amd64
Dependencies:
bdb: 4.7.25
GNU-iconv: 1.13.1
apr: 1.4.5
apr-util: 1.3.12
httpd: 2.2.19
neon: 0.29.6
serf: 0.7.x
cyrus-sasl: 2.1.23
sqlite: 3070603
openssl: 1.0.0a
swig: 1.3.36
python: 2.6.6
perl: 5.12.2
ruby: 1.8.7
Signatures:
subversion-1.7.0-alpha1.tar.gz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (OpenBSD)
iEYEABECAAYFAk3qqzYACgkQ5dMCc/WdJfANXgCg+J6Lx46qm1b8Vy/HtSsTi1Ny
gIkAniWR6e3qb8P1IEpW5JK44ALUH427
=R84Y
-----END PGP SIGNATURE-----
subversion-1.7.0-alpha1.tar.bz2
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (OpenBSD)
iEYEABECAAYFAk3qq2kACgkQ5dMCc/WdJfD8SQCghBbsvq8RTqtF5yuwtZYrpyo4
5iAAoLmBRyXxlhFjksDLV4TTQZxTk/7k
=U6X+
-----END PGP SIGNATURE-----