Page MenuHomePhabricator

Mark IMPORTED_CHANGE more consistently
ClosedPublic

Authored by epriestley on Nov 1 2013, 3:55 PM.
Tags
None
Referenced Files
F13297055: D7470.id16839.diff
Fri, Jun 7, 12:25 AM
F13295708: D7470.id16841.diff
Thu, Jun 6, 7:13 AM
F13295680: D7470.id16840.diff
Thu, Jun 6, 6:50 AM
F13267244: D7470.diff
Wed, May 29, 3:03 AM
F13252642: D7470.diff
Sat, May 25, 1:55 AM
F13232542: D7470.id16839.diff
Tue, May 21, 1:21 AM
F13230536: D7470.diff
Mon, May 20, 11:02 PM
F13229806: D7470.id.diff
Mon, May 20, 7:11 PM
Subscribers

Details

Reviewers
btrahan
Commits
Restricted Diffusion Commit
rPd1649d176f67: Mark IMPORTED_CHANGE more consistently
Summary

See https://github.com/facebook/phabricator/issues/425. There are some ways that the change parsers may not reach finishParse(), but we now need them to in order to mark the commit imported, advance the progress bar, and eventually kick the repository out of IMPORTING status.

Take all the copy/pasted code in the parsers and move it into the parent. Specifically, this is:

  • Printing a status message about starting a parse;
  • checking for bad commits;
  • queueing the next parse stage; and
  • marking the import step complete.
Test Plan

Used reparse.php --change to reparse Git, SVN and Mercurial repos.

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

epriestley updated this revision to Unknown Object (????).Nov 1 2013, 3:57 PM

Smaller diff.