Re: Call for testing: cvs2bzr

On Tue, Aug 25, 2009 at 4:12 PM, Michael Haggerty<[email protected]> wrote:
> Regarding the build failures for cvs2svn release 2.2.0, my guess is that
> the problem is deprecation warnings from a new Python version, but the
> error log doesn't include enough information to be sure.  (The output
> from "run-tests.py -v" would be helpful.)
>
> There is a reasonable chance that the problem has already been fixed in
> cvs2svn release 2.3.0, and if not I'd be happy to work with the packager
> to iron out any wrinkles.  (But I don't have a karmic system to test on.)

I have an up-to-date karmic system, and I've run the full test suite
on it a couple of times with just the usual "XFAIL" expected failures.
 Let me know if I can help by, umm, running the tests again.  Or
anything else.  ;-)

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.

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.

Greg

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

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