- removed comment
Unable to complete an ET checkout without SVN network errors
Issue #233
closed
I am running an automated build and test system every night which attempts to check out the Einstein Toolkit thornlist. Every night, I get error messages from at least one thorn of the form:
Checking out module: CactusNumerical/Cartoon2D from repository: http://svn.cactuscode.org/arrangements/CactusNumerical/Cartoon2D/trunk into: ./arrangements svn: REPORT of '/arrangements/CactusNumerical/Cartoon2D/!svn/vcc/default': Could not read response body: connection was closed by server. (http://svn.cactuscode.org)
Typically, three or more thorns will exhibit this problem. All the following repositories have exhibited this problem since 11th January 2011:
CactusArchive/ADM CactusElliptic/EllBase CactusNumerical/Cartoon2D CactusNumerical/Dissipation CactusNumerical/InterpToArray CactusNumerical/RotatingSymmetry180 CactusNumerical/RotatingSymmetry90 EinsteinInitialData/Exact EinsteinInitialData/IDAnalyticBH EinsteinInitialData/TOVSolver EinsteinInitialData/TwoPunctures LSUThorns/QuasiLocalMeasures manifest simfactory
I assume that there is some problem with the SVN server or our network connection to it that is making it so unreliable. Am I the only one?
Keyword:
Comments (3)
-
-
reporter
- changed status to resolved
- removed comment
GetComponents now returns an error code indicating if the checkout was successful, and it is straightforward to repeat the checkout if not. I am also not experiencing this problem frequently anymore, so I am closing the ticket.
-
- edited description
- changed status to closed
- Log in to comment
I don't have a good answer, but only some ideas: Do you use http for that checkout, or https? If it is http: check with the AEI (or wherever you run this) if http connections are cached by something like a transparent proxy. It could be that the http connections last simply too long for a proxy. https would bypass the proxy. Alternatively you could also try to checkout some other large public repository to check if this fails as well (if this is a client-side or server-side problem).
I didn't see this yet, even with complete checkouts.