[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: r978841 - in /subversion/trunk/subversion/tests/cmdline: svnrdump_tests.py svnrdump_tests_data/ svnrdump_tests_data/revision0.dump

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Sat, 24 Jul 2010 13:30:10 +0300

artagnon_at_apache.org wrote on Sat, Jul 24, 2010 at 10:18:58 -0000:
> + # Create a dump file using svnrdump
> + r, svnrdump_dumpfile, err = svntest.main.run_svnrdump(sbox.repo_url)
> +
> + # Check error code
> + if (r != 0):
> + raise svntest.Failure('Result code not 0')
> +
> + # Check the output from stderr
> + if not err[0].startswith('* Dumped revision'):
> + raise svntest.Failure('No valid output')

Not your fault, but that's not what I meant. What I meant was to check for no
unexpected stderr (e.g., no "svn: warning %s" or similar).

For example, you could do that by running 'svnrdump -q' and then verifying that
*nothing* was printed to stderr.

Makes sense?
Received on 2010-07-24 12:31:52 CEST

This is an archived mail posted to the Subversion Dev mailing list.