- **status**: in-progress --> review - **Comment**: Added to development.ini in db/7857
Email contents come from an event handler hook, so fix for that is internal to SF in forge-classic:db/7857 --- ** [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:** Wed Mar 25, 2015 10:34 AM 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.
