- **status**: review --> in-progress - **Comment**: I think we need to add description of new options (`scm.import.retry_count` & `scm.import.retry_sleep_secs`) to `development.ini`.
Email to `sfengine...@slashdotmedia.com` contains failure details, but shows "None" instead of import source (I guess this is old bug, but can be fixed now). Admin email shows source just fine. sfengineers email: ~~~~ Forking/cloning repo t7857 in project test from None failed. ~~~~ admin email: ~~~~ Forking/cloning repo t7857 in project test from https://svn.code.sf.net/u/jetmind/test-svn failed. The SourceForge engineering team has been notified. ~~~~ Other than that all works fine for me. --- ** [tickets:#7857] Retry svnsync repo clone failures** **Status:** in-progress **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:02 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.
