D10945: test: clarify some output in `test-transaction-rollback-on-sigpipe`
marmoute (Pierre-Yves David)
phabricator at mercurial-scm.org
Sat Jul 3 01:42:03 UTC 2021
marmoute created this revision.
Herald added a reviewer: hg-reviewers.
Herald added a subscriber: mercurial-patches.
REVISION SUMMARY
We don't want a dirty transaction to remain, but need to check the transaction
was aborted. Otherwise it is easy to have no abandoned transaction if the
transaction succeed.
REPOSITORY
rHG Mercurial
BRANCH
default
REVISION DETAIL
https://phab.mercurial-scm.org/D10945
AFFECTED FILES
tests/test-transaction-rollback-on-sigpipe.t
CHANGE DETAILS
diff --git a/tests/test-transaction-rollback-on-sigpipe.t b/tests/test-transaction-rollback-on-sigpipe.t
--- a/tests/test-transaction-rollback-on-sigpipe.t
+++ b/tests/test-transaction-rollback-on-sigpipe.t
@@ -50,12 +50,16 @@
> pretxnchangegroup.break-things=$hook_script
> EOF
+ $ hg --cwd ./remote tip -T '{node|short}\n'
+ 000000000000
$ cd local
$ echo foo > foo ; hg commit -qAm "commit"
$ hg push -q -e "\"$PYTHON\" \"$TESTDIR/dummyssh\"" --remotecmd $remotecmd 2>&1 | grep -v $killable_pipe
abort: stream ended unexpectedly (got 0 bytes, expected 4)
The remote should be left in a good state
+ $ hg --cwd ../remote tip -T '{node|short}\n'
+ 000000000000
$ hg --cwd ../remote recover
no interrupted transaction available
[1]
To: marmoute, #hg-reviewers
Cc: mercurial-patches, mercurial-devel
More information about the Mercurial-devel
mailing list