#2 Connection broken from server during unit tests

v0.3
closed-works-for-me
Connection (2)
5
2003-10-15
2003-06-21
No

The unit tests frequently fail against the sourceforge
cvs server. The same batched unit tests will
consistently pass against a cvs repository on a local
area network (lan).

To replicate this behaviour have the tests point at a
sf.net cvs server. Use the nunit gui to repeatedly
test the CvsServerConnectionTest.MakeConnection_Good
test. Sometimes the test will succeed, sometimes it
will fail.

Discussion

  • Clayton Harbour

    Clayton Harbour - 2003-07-17

    Logged In: YES
    user_id=677222

    Not an issue. The problem happens with most cvs clients and
    seems to be a problem with the sf.net cvs servers. The
    interm solution was to point the unit tests at a different
    cvs server.

     
  • Clayton Harbour

    Clayton Harbour - 2003-07-17
    • status: open --> open-invalid
     
  • Clayton Harbour

    Clayton Harbour - 2003-07-17
    • status: open-invalid --> open-works-for-me
     
  • Clayton Harbour

    Clayton Harbour - 2003-10-15
    • status: open-works-for-me --> closed-works-for-me
     
  • Clayton Harbour

    Clayton Harbour - 2003-10-15

    Logged In: YES
    user_id=677222

    There was/ is a known problem with sourceforge anonymous
    connections. The resolution to this issue has involved the
    following steps:
    1) set up an anonymous cvs server that is not under as
    much load as the sf.net servers and point the unit tests at
    these
    2) add a configuration section to the unit tests to
    allow a user to point the unit tests at their own local host

    This has reduced/ minimized the problems with tests failing
    due to network issues.

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks