sapling/hgext/p4fastimport
Kaley Huang 667f296601 bring back mercurial worker
Summary:
We disabled `runworker` for every importer (fastimport, syncimport, seqimport) when we hotfixed a customized file transaction breakage in fastimport D7108127.

Since
- we're not using fastimport, which relies on the customized file transaction
- seqimport does not rely on the customized file transaction mechanism
- syncimport is super slow without `runworker` and syncimport does not rely on the customized file transaction mechanism
- the manual work involved in adding mapping to ovrsource (we have to do that if we don't have syncimport) is not trivial

I think it's a good idea to bring back `runworker`, which is a configurable config, and it's explicitly set to `false` for fastimport and seqimport, `force` for syncimport.

This diff
- make the `useworker` config available again
- remove the unnecessary test on the customized file transaction, which is still broken with `runworker`
- log the time it takes to finish one sync import

Differential Revision: D7557856

fbshipit-source-id: 6d4105cc38b182e027512730901ce3b2a4e1d449
2018-04-13 21:51:51 -07:00
..
__init__.py Feedback 2018-04-13 21:51:44 -07:00
filetransaction.py fb-hgext: move most of hgext3rd and related tests to core 2018-01-09 03:03:59 -08:00
importer.py Get file contents from local storage if possible 2018-04-13 21:51:45 -07:00
lfs.py Deal with large files and their metadata 2018-04-13 21:51:44 -07:00
p4.py Copy tracing 2018-04-13 21:51:43 -07:00
seqimporter.py Get file contents from local storage if possible 2018-04-13 21:51:45 -07:00
util.py bring back mercurial worker 2018-04-13 21:51:51 -07:00