You are viewing a plain text version of this content. The canonical link for it is here.
Posted to scm-dev@maven.apache.org by "Dennis Lundberg (JIRA)" <ji...@codehaus.org> on 2005/12/28 19:49:27 UTC

[jira] Commented: (SCM-121) Intermittent CVS test failures

    [ http://jira.codehaus.org/browse/SCM-121?page=comments#action_54368 ] 

Dennis Lundberg commented on SCM-121:
-------------------------------------

I am experiencing this as well. My environment is Windows XP using cvsnt as my command-line client.

Mike wrote about this error on the dev-list:

org.apache.maven.scm.provider.cvslib.command.checkout.CvsCheckoutCommandTest

junit.framework.AssertionFailedError: expected:<38403> but was:<39511> 	
at junit.framework.Assert.fail(Assert.java:47) 	
at junit.framework.Assert.failNotEquals(Assert.java:282) 	
at junit.framework.Assert.assertEquals(Assert.java:64) 	
at junit.framework.Assert.assertEquals(Assert.java:136) 	
at junit.framework.Assert.assertEquals(Assert.java:142) 	
at org.apache.maven.scm.provider.cvslib.command.checkout.CvsCheckoutCommandTest.testCheckOutWithTag(CvsCheckoutCommandTest.java:88)  

After some investigation I have concluded that this happens in a Windows environment because the command-line cvs client checks out the file with windows line-endings (CR LF). This makes the total size of the file in bytes larger than it would in a unix environment. That is what the error above is telling us.

I googled and found the CVS-book at
http://cvsbook.red-bean.com/cvsbook.html#CVS%20is%20not%20doing%20line-end%20conversion%20correctly

They seem to imply that the only way of stopping a cvs client from converting line-endings to the native sort is to say that the file is binary. That would mean specifying -kb in the CVS/Entries file. So I tried this and created such a directory and file in the test repository, but the results were the same.

I am trying to make improvements to the cvs provider but I'm having all sorts of trouble just building maven-scm, being on Windows and not having a default locale of English. It's quite frustrating.

To move forward, SCM-10 talks about switching from command line cvs to cvslib. This would be a major improvement for compatibility. There is a gotcha that cvslib might not support the ext transport. If that is the case, do you think it would be possible to use command line cvs for ext transport and cvslib for the rest?

> Intermittent CVS test failures
> ------------------------------
>
>          Key: SCM-121
>          URL: http://jira.codehaus.org/browse/SCM-121
>      Project: Maven SCM
>         Type: Bug

>   Components: maven-scm-provider-cvs
>     Versions: 1.0-beta-3
>     Reporter: mike perham
>      Fix For: 1.0-beta-3

>
>
> Dan and I continue to have test failures when trying to compile the cvs plugin in our environment.  I emailed these problems to the scm-dev list about a week ago.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira