Discussion:
Failing tests
Olaf Meeuwissen
2013-03-12 01:21:18 UTC
Permalink
Hi,

I've just checked out ***@5419 and ran a `make check` before I start
looking at making some local changes for use with CVSNT. Much to my
surprise three of the tests failed (log attached). I'm running this on
Debian wheezy (last updated on 2013-03-11) with Debian's CVS package.
I also have the Debian cvs2svn package installed in case that matters.

$ dpkg-query -W cvs cvs2svn
cvs 2:1.12.13+real-9
cvs2svn 2.3.0-3

The tests that are failing are:

XFAIL: run-tests.py 87: reveal a second bug that created a branch twice
XFAIL: run-tests.py 129: optimal tag after deleting files
XFAIL: run-tests.py 163: check adding .cvsignore to an existing branch

Is this a known problem? Any idea what might be wrong (and how to fix
it)?

FTR, repeating this exercise with cvsnt[1] shows the exact same failures
with no other tests failing. That is, the log is byte-for-byte the same
(checked with diff).

[1] Built from the files available at

http://cvsnt.sourcearchive.com/downloads/2.5.04.3236-1.2/

and started cvslockd with

# sed -i '/START_CVSLOCKD=/s/no/yes/' /etc/default/cvsnt
# invoke-rc.d cvsnt start

before running `make check`.

Thanks in advance,
--
Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS CORPORATION
FSF Associate Member #1962 Help support software freedom
http://www.fsf.org/jf?referrer=1962

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

To unsubscribe from this discussion, e-mail: [dev-***@cvs2svn.tigris.org].
Michael Haggerty
2013-03-12 08:20:18 UTC
Permalink
Post by Olaf Meeuwissen
looking at making some local changes for use with CVSNT. Much to my
surprise three of the tests failed (log attached). [...]
XFAIL: run-tests.py 87: reveal a second bug that created a branch twice
XFAIL: run-tests.py 129: optimal tag after deleting files
XFAIL: run-tests.py 163: check adding .cvsignore to an existing branch
Is this a known problem? Any idea what might be wrong (and how to fix
it)?
"XFAIL" means "expected failure". These are minor known problems in
cvs2svn that nobody has gotten around to fixing/improving.

You don't need to worry unless you see "FAIL" (unexpected failure) or to
a lesser extent "XPASS" (test expected to fail passed unexpectedly).

Michael
--
Michael Haggerty
***@alum.mit.edu
http://softwareswirl.blogspot.com/

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

To unsubscribe from this discussion, e-mail: [dev-***@cvs2svn.tigris.org].
Olaf Meeuwissen
2013-03-12 23:31:03 UTC
Permalink
Post by Michael Haggerty
Post by Olaf Meeuwissen
looking at making some local changes for use with CVSNT. Much to my
surprise three of the tests failed (log attached). [...]
XFAIL: run-tests.py 87: reveal a second bug that created a branch twice
XFAIL: run-tests.py 129: optimal tag after deleting files
XFAIL: run-tests.py 163: check adding .cvsignore to an existing branch
Is this a known problem? Any idea what might be wrong (and how to fix
it)?
"XFAIL" means "expected failure". These are minor known problems in
cvs2svn that nobody has gotten around to fixing/improving.
You don't need to worry unless you see "FAIL" (unexpected failure) or to
a lesser extent "XPASS" (test expected to fail passed unexpectedly).
Thanks for the clarification.
--
Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS CORPORATION
FSF Associate Member #1962 Help support software freedom
http://www.fsf.org/jf?referrer=1962

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

To unsubscribe from this discussion, e-mail: [dev-***@cvs2svn.tigris.org].
Loading...