allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Brondsema" <d...@brondsema.net>
Subject [allura:tickets] #7857 Retry svnsync repo clone failures
Date Mon, 23 Mar 2015 17:08:05 GMT
- **status**: in-progress --> review
- **Comment**:

On branch db/7857

To test, import an SVN repo and force an error (e.g. tweak command to use invalid arguments;
or kill the svnsync command).  Make sure that it logs appropriately and tries again.  It should
succeed if possible, or if it can't succeed then the failure email should still have the failure
details.



---

** [tickets:#7857] Retry svnsync repo clone failures**

**Status:** review
**Milestone:** unreleased
**Labels:** sf-current sf-2 
**Created:** Thu Mar 19, 2015 02:57 PM UTC by Dave Brondsema
**Last Updated:** Mon Mar 23, 2015 03:37 PM UTC
**Owner:** Dave Brondsema

Repo clone tasks may fail due to 'svnsync' failing (remote server timeout or random error,
etc).  We should be smart about retrying those.  Other failures that are a result of our code
can happen too (failure to parse author, or timestamp properly) and it doesn't make sense
to retry those.

I don't know about git/hg transfer errors.  SVN seems to be the most common


---

Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options.
 Or, if this is a mailing list, you can unsubscribe from the mailing list.
Mime
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message