This is an archive of the discontinued Mercurial Phabricator instance.

run-tests: update back to original node after bisecting
AbandonedPublic

Authored by quark on Oct 5 2017, 12:22 AM.

Details

Reviewers
ryanmce
Group Reviewers
hg-reviewers
Summary

The bisect operation should have minimal side-effect.

Diff Detail

Repository
rHG Mercurial
Lint
Lint Skipped
Unit
Unit Tests Skipped

Event Timeline

quark created this revision.Oct 5 2017, 12:22 AM
ryanmce requested changes to this revision.Oct 12 2017, 7:34 AM
ryanmce added a subscriber: ryanmce.

I'm +1 on this series and the rest looks fine but I think this one needs some improvements before landing.

tests/run-tests.py
2114–2115

It feels fragile to rely on the output of a debug flag command to determine state. Can you use hg status instead?

2115–2145

For readability, please add the try/finally (with the finally block being just pass for now) in a separate patch.

2119–2120

When does this happen? Add a comment, perhaps? I'd also prefer a more explanatory output.

This revision now requires changes to proceed.Oct 12 2017, 7:34 AM
quark added inline comments.Oct 12 2017, 11:34 AM
tests/run-tests.py
2115–2145

During the meeting deciding to experiment with Phabricator, I think we agreed that with Phabricator's ability to diff with whitespaces ignored and its yellow margins of "Moved from line X", the patch size standard could be more flexible.

quark updated this revision to Diff 2649.Oct 12 2017, 8:11 PM
ryanmce added inline comments.Oct 13 2017, 10:51 AM
tests/run-tests.py
2115–2145

I suppose, I ended up using that ability but it would still help readability either way. I won't fuss too much over it.

ryanmce accepted this revision as: ryanmce.Oct 13 2017, 11:08 AM

I like this overall; but I don't feel I can queue a new flag to bisect without input from the rest of the community.

quark abandoned this revision.Oct 17 2017, 1:00 AM