Re: POST-commit hook issue - Check in works

2014-02-09 Thread Ben Reser
On 2/9/14, 2:30 PM, Matt Parks wrote: > This was working, I attempted to add LDAP and had no luck getting it to work. > I have rolled back code and at this point I have tried so many things that I > am not able to get it working again and my team will be in tomorrow and need > this to work. > > I

Regresson on trunk with SQLite 3.8 [was: Re: 1.8.6 up for testing/signing]

2014-02-09 Thread Branko Čibej
> I just wonder when we started to rely on a particular query plan. It turns out to be more complex than that. I started bisecting to find the revision that broke trunk, and found that in r1542765, op-depth-test changed its failure mode from, e.g., /Users/brane/src/svn/repos/trunk/subversion/li

POST-commit hook issue - Check in works

2014-02-09 Thread Matt Parks
OK, information on my issue, svn, version 1.6.11 (r934486) compiled Apr 12 2012, 11:02:08 COMMIT code works, but post-commit does not. Here is my post commit code: echo "=" >> ${LOG} echo "${REPOS_NAME} r${REV} ${DATE} $(${SVN}look author -r ${REV} $REPOS)" >> $

Re: 1.8.6 up for testing/signing

2014-02-09 Thread Branko Čibej
On 09.02.2014 22:26, Ben Reser wrote: > On 2/9/14, 8:06 AM, Branko Čibej wrote: >> I just tested the 1.8.5 release tarball in exactly the same environment. All >> tests pass (except for wc-queries-test #3, which we know did not work with >> SQLite 3.8.x in 1.8.5). >> >> As far as I'm concerned, thi

[svnbench] Revision: 1566478 compiled Feb 10 2014, 00:22:07 on x86_64-unknown-linux-gnu

2014-02-09 Thread neels
1.8.0@1492600 vs. trunk@1566230 Started at Mon Feb 10 00:27:44 UTC 2014 *DISCLAIMER* - This tests only file://-URL access on a GNU/Linux VM. This is intended to measure changes in performance of the local working copy layer, *only*. These results are *not* generally true for everyone. Charts of t

Re: 1.8.6 up for testing/signing

2014-02-09 Thread Ben Reser
On 2/9/14, 8:06 AM, Branko Čibej wrote: > I just tested the 1.8.5 release tarball in exactly the same environment. All > tests pass (except for wc-queries-test #3, which we know did not work with > SQLite 3.8.x in 1.8.5). > > As far as I'm concerned, this proves conclusively that 1.8.6 has a serio

Re: 1.8.6 up for testing/signing

2014-02-09 Thread Branko Čibej
On 09.02.2014 14:00, Branko Čibej wrote: > On 09.02.2014 02:34, Ben Reser wrote: >> On 2/8/14, 2:42 PM, Branko Čibej wrote: >>> Many tests fail on OSX with SQLite 3.8.3. See the attached log. >> I ran a set of tests with OS X 10.9.1 and SQLite 3.8.3 amalgamation and it >> completed successfully. I

Re: 1.7.15 up for testing/signing

2014-02-09 Thread Branko Čibej
Summary: +1 to release Platform Mac OS X 10.9.1 Mavericks, build 13B42 Standard dependencies: Apple clang(++) 5.0 (clang-500.2.79)/LLVM 3.3svn APR 1.4.5 APR-Util 1.3.12 zlib 1.2.5 httpd 2.2.24 OpenSSL 0.9.8y Python 2.7.5 Perl 5.16.2

Re: 1.8.6 up for testing/signing

2014-02-09 Thread Branko Čibej
On 09.02.2014 11:58, Branko Čibej wrote: > On 09.02.2014 11:21, Bert Huijben wrote: >> Are you 100% sure you tested a clean branch version. Most of these >> specific tests are XFail on trunk since I added a write lock test in >> the move update logic a few weeks ago, but this lock test shouldn't >>

Re: 1.8.6 up for testing/signing

2014-02-09 Thread Branko Čibej
On 09.02.2014 02:34, Ben Reser wrote: > On 2/8/14, 2:42 PM, Branko Čibej wrote: >> Many tests fail on OSX with SQLite 3.8.3. See the attached log. > I ran a set of tests with OS X 10.9.1 and SQLite 3.8.3 amalgamation and it > completed successfully. I notice a lot of your tests have an error or wa

Re: 1.8.6 up for testing/signing

2014-02-09 Thread Branko Čibej
On 09.02.2014 11:21, Bert Huijben wrote: > Are you 100% sure you tested a clean branch version. Most of these > specific tests are XFail on trunk since I added a write lock test in > the move update logic a few weeks ago, but this lock test shouldn't be > merged to the 1.8 branch (yet) as we haven'

Re: 1.8.6 up for testing/signing

2014-02-09 Thread Bert Huijben
Are you 100% sure you tested a clean branch version. Most of these specific tests are XFail on trunk since I added a write lock test in the move update logic a few weeks ago, but this lock test shouldn't be merged to the 1.8 branch (yet) as we haven't fixed the code that triggers this problem.