Opened 8 years ago

Last modified 8 years ago

#84 accepted enhancement

Make GetComponents robust to transient network errors

Reported by: Ian Hinder Owned by: Eric Seidel
Priority: minor Milestone:
Component: GetComponents Version:
Keywords: Cc:


I am running automated nightly checkouts using GetComponents, and every so often the checkout will fail with an error such as

Checking out module: CactusArchive/ADM

from repository:

into: ./arrangements

svn: REPORT of '/arrangements/CactusArchive/ADM/!svn/vcc/default': Could not read response body: connection was closed by server. (

These errors are transient and go away if you retry. Would it be possible to add some logic into GetComponents to make a note of those thorns which failed to check out due to such errors and to try them again at the end of the checkout? An immediate retry might run into the same problem again.

Attachments (0)

Change History (1)

comment:1 Changed 8 years ago by Eric Seidel

Status: newaccepted

Do you know if all errors of the form "svn: REPORT" are recoverable? I assume there are multiple such errors, and it would be nice if there were a general regex that would recognize all of them. On the other hand, I could just retry all errors at the end of the checkout, but that would probably be pointless if all, or the majority of components failed checkout.

Modify Ticket

Change Properties
Set your email in Preferences
as accepted The owner will remain Eric Seidel.
Next status will be 'review'.
as The resolution will be set.
to The owner will be changed from Eric Seidel to the specified user.
The owner will be changed from Eric Seidel to anonymous.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.