When checking the bundle contents against the revisions it is being rebased
over, include the sources of renames, as changes made in those files also
conflict with the bundle.
Details
- Reviewers
ryanmce durham quark - Group Reviewers
Restricted Project - Commits
- rFBHGXa1cd7effe38a: pushrebase: check sources of renames when looking for conflicts
Diff Detail
- Repository
- rFBHGX Facebook Mercurial Extensions
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Event Timeline
Since this is sensitive to push throughput, we need to be more careful here.
hgext3rd/pushrebase.py | ||
---|---|---|
549 | This is fast because it just reads the changelog. | |
552–558 | This is not that fast since it looks up file from manifest and extracts the file content. | |
833 | The below (including _getrevs) is in a critical section (taking the SQL lock) that affects push throughput. We can pre-calcualte the renamed information before entering the critical section, and cache them per revision. |
I fixed the failing test. Looks like it was always a bad test, and this diff just exposed it.
This is fast because it just reads the changelog.