Mercurial > hg
changeset 47555:452795b0b69a
test: clarify some output in `test-transaction-rollback-on-sigpipe`
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.
Differential Revision: https://phab.mercurial-scm.org/D10945
| author | Pierre-Yves David <pierre-yves.david@octobus.net> |
|---|---|
| date | Fri, 02 Jul 2021 20:22:56 +0200 |
| parents | c8f8d2dba6c7 |
| children | 640fdb7fd67b |
| files | tests/test-transaction-rollback-on-sigpipe.t |
| diffstat | 1 files changed, 4 insertions(+), 0 deletions(-) [+] |
line wrap: on
line diff
--- a/tests/test-transaction-rollback-on-sigpipe.t Tue Jun 29 13:58:18 2021 -0700 +++ b/tests/test-transaction-rollback-on-sigpipe.t Fri Jul 02 20:22:56 2021 +0200 @@ -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]