Tom Bing wrote on Tue, May 01, 2012 at 20:04:41 -0400:
> I appreciate your advice, I'll check the SVNKit lists.
>
> Judging from the access timestamps (ls -lu jsvn*) the "jsvnadmin"
> script was the only one that had been accessed when this
> basic_tests.py run failed.
Not surprising; 'svnadmin c
I appreciate your advice, I'll check the SVNKit lists.
Judging from the access timestamps (ls -lu jsvn*) the "jsvnadmin"
script was the only one that had been accessed when this
basic_tests.py run failed. This run, if successful, would have gone
through all the tests.
Regards,
Tom
On Tue, May 1
Tom Bing wrote on Tue, May 01, 2012 at 12:04:03 -0400:
> I am running some tests with basic_tests.py to verify the operation of
> the SVNKit command-line client scripts. I encountered an error (Errno
> 8) when I ran basic_tests.py with the --use-jsvn
SVNKit questions should be asked on the SVNKit
I am running some tests with basic_tests.py to verify the operation of
the SVNKit command-line client scripts. I encountered an error (Errno
8) when I ran basic_tests.py with the --use-jsvn and --bin= options,
as shown by the terminal session below.
[tom@lorien ~]$ pwd
/home/tom
[tom@lorien ~]$
Daniel Shahaf wrote on Mon, Apr 30, 2012 at 17:13:06 +0300:
> Tom Bing wrote on Mon, Apr 30, 2012 at 09:55:33 -0400:
> > Folks, I did try to study the testing READMEs and the info at
> > http://subversion.apache.org/docs/community-guide/building.html before I
> > posted here. I have recently Googl
Tom Bing wrote on Mon, Apr 30, 2012 at 09:55:33 -0400:
> Hi Folks,
>
> The earlier guidance was a great help. Specifically, this info from Daniel
> on Apr 28:
>
> > *_tests.py look by default for svn in ../../svn/svn --- i.e., build
> > outputs. Are you running from a built source tree? If not,
Hi Folks,
The earlier guidance was a great help. Specifically, this info from Daniel
on Apr 28:
> *_tests.py look by default for svn in ../../svn/svn --- i.e., build
> outputs. Are you running from a built source tree? If not, pass
> --bin=/usr/bin.
By using --bin=, I was able to run the tests
On Sun, Apr 29, 2012 at 8:54 AM, Daniel Shahaf wrote:
> Nico Kadel-Garcia wrote on Sun, Apr 29, 2012 at 08:48:27 -0400:
> > On Sun, Apr 29, 2012 at 1:31 AM, Daniel Shahaf >wrote:
> >
> > > Nico Kadel-Garcia wrote on Sat, Apr 28, 2012 at 21:38:59 -0400:
> > >
> > > > > SKIP and XFAIL are not error
Nico Kadel-Garcia wrote on Sun, Apr 29, 2012 at 08:48:27 -0400:
> On Sun, Apr 29, 2012 at 1:31 AM, Daniel Shahaf wrote:
>
> > Nico Kadel-Garcia wrote on Sat, Apr 28, 2012 at 21:38:59 -0400:
> >
> > > > SKIP and XFAIL are not errors. FAIL are errors. XPASS are not
> > supposed
> > > > to happen i
On Sun, Apr 29, 2012 at 1:31 AM, Daniel Shahaf wrote:
> Nico Kadel-Garcia wrote on Sat, Apr 28, 2012 at 21:38:59 -0400:
>
> > > SKIP and XFAIL are not errors. FAIL are errors. XPASS are not
> supposed
> > > to happen in release tarballs, but if they do they are treated like
> FAIL
> > > is for t
Nico Kadel-Garcia wrote on Sat, Apr 28, 2012 at 21:38:59 -0400:
> On Sat, Apr 28, 2012 at 5:27 PM, Daniel Shahaf wrote:
>
> > Nico Kadel-Garcia wrote on Sat, Apr 28, 2012 at 16:56:54 -0400:
> > > If you're up for some testing, there are tools I've submitted to
> > Repoforge
> > > for building 1.6.
On Sat, Apr 28, 2012 at 5:27 PM, Daniel Shahaf wrote:
> Nico Kadel-Garcia wrote on Sat, Apr 28, 2012 at 16:56:54 -0400:
> > If you're up for some testing, there are tools I've submitted to
> Repoforge
> > for building 1.6.18 and 1.7.4 over at http://www.github.com/nkadel/ All
> the
> > patches and
Nico Kadel-Garcia wrote on Sat, Apr 28, 2012 at 16:56:54 -0400:
> If you're up for some testing, there are tools I've submitted to Repoforge
> for building 1.6.18 and 1.7.4 over at http://www.github.com/nkadel/ All the
> patches and .spec files for building the RPM's, compatble for RHEL 4, 5,
> and
If you're up for some testing, there are tools I've submitted to Repoforge
for building 1.6.18 and 1.7.4 over at http://www.github.com/nkadel/ All the
patches and .spec files for building the RPM's, compatble for RHEL 4, 5,
and 6. You could rsync the repository to a new environment, build and
insta
As to "how could I know this" --- *_tests.py take a --help option,
which lists --bin in its output.
*_tests.py look by default for svn in ../../svn/svn --- i.e., build
outputs. Are you running from a built source tree? If not, pass
--bin=/usr/bin.
I have a Subversion 1.6.15 repository set up and working on an Intel
64-bit RHEL5 Linux platform. I have been trying unsuccessfully to run
the command-line test suite, using
subversion/tests/cmdline/basic_tests.py. The version of Python on
this server is 2.4.3. This script runs normally with the
17 matches
Mail list logo
