Re: Call for testing: cvs2bzr

Greg Ward wrote:
> On this machine, /usr/bin/python is 2.6.2-0ubuntu1, and I didn't get
> any deprecation warnings from run-tests.py.  Ian, where are those
> build logs again?  I thought you provided a link, but couldn't find it
> just now.

The build failures were for 2.2.0, which didn't yet have the changes to
avoid DeprecationWarnings when running under Python 2.6.  Thanks for the
confirmation that the warnings really are gone in cvs2svn 2.3.0.

> Also: might be a good idea to add --skip-expected-failures to
> run-tests.  Those upstream packagers have funny ideas about builds
> with stack traces or the word "FAIL" in them.  If we could turn those
> off for particularly paranoid builds, it might make it easier to get
> newer versions of cvs2svn into Linux distros.

This is a good idea.  We use the testing framework from the Subversion
project (a decision, BTW, whose wisdom is becoming ever less obvious).
So we would have to make any such changes in a way that is acceptable to
them, too.  OTOH I am a committer on the svntest stuff, so there would
be a good chance of getting it in :-)

We could simply design our own substitute for XFail.  The problem is
that the command-line-option processing is done within the Subversion
test framework, and I don't think there are any hooks into it.  So it
wouldn't be as trivial as one would hope to get the
--skip-expected-failures option processed.

Michael

------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1667&dsMessageId=2387435

To unsubscribe from this discussion, e-mail: [[email protected]].