In "bin/repository reparse", continue on "PhabricatorWorkerPermanentFailureException"

Summary:
Fixes T13315. See that task for discussion.

Without `--background`, we currently treat this as a catastrophic failure, but it's relatively routine for some repository states. We can safely continue reparsing other steps.

Test Plan: Ran `bin/repository reparse --all X --message` with commits faked to all be unreachable. Got warnings instead of a hard failure on first problem.

Reviewers: amckinley

Reviewed By: amckinley

Maniphest Tasks: T13315

Differential Revision: https://secure.phabricator.com/D20588

src/applications/repository/management/PhabricatorRepositoryManagementReparseWorkflow.php

@@ -252,12 +252,24 @@ final class PhabricatorRepositoryManagementReparseWorkflow
       );
 
       foreach ($classes as $class) {
-        PhabricatorWorker::scheduleTask(
+        try {
-          $class,
+          PhabricatorWorker::scheduleTask(
-          $spec,
+            $class,
-          array(
+            $spec,
-            'priority' => PhabricatorWorker::PRIORITY_IMPORT,
+            array(
-          ));
+              'priority' => PhabricatorWorker::PRIORITY_IMPORT,
+            ));
+        } catch (PhabricatorWorkerPermanentFailureException $ex) {
+          // See T13315. We expect some reparse steps to occasionally raise
+          // permanent failures: for example, because they are no longer
+          // reachable. This is a routine condition, not a catastrophic
+          // failure, so let the user know something happened but continue
+          // reparsing any remaining commits.
+          echo tsprintf(
+            "<bg:yellow>** %s **</bg> %s\n",
+            pht('WARN'),
+            $ex->getMessage());
+        }
       }
 
       $progress->update(1);