They are mostly equivalent to the corresponding chg options.
For now, many tests are still failing in this configuration.
It is *not* run on CI.
Details
- Reviewers
Alphare marmoute pulkit - Group Reviewers
hg-reviewers - Commits
- rHGfb2368598281: tests: Add `--rhg` and `--with-rhg=<path>` options for `run-tests.py`
Diff Detail
- Repository
- rHG Mercurial
- Branch
- default
- Lint
No Linters Available - Unit
No Unit Test Coverage
Event Timeline
I intentionally placed this patch (D10095) in a stack on top of D10094 as it is based on the premise that what the parent does is done. Now the discussion in D10094 is leaning towards doing something different instead, and ideally this patch would also be affected. But it has already been merged, before its parent. Also the default branch is in a broken state at the moment (though CI for this is not enabled yet).
Now admittedly some other patches in this stack *are* truly independent (in terms of semantics, not just lack of merge conflict) and can be merged in any order and it may not be obvious which is which. Still, I feel that this Phabricator workflow is problematic and wish for Merge Requests where the submitter can designate which sequences of commits are to be merged atomically.