Mercurial > hg
view tests/test-legacy-exit-code.t @ 48998:91a60031aba2 stable
dispatch: fix silly blackbox entries when hg is interrupted
When hg is interrupted, it creates ui.log like this:
1970/01/01 00:00:00 user @0000000000000000000000000000000000000000 (62488)> killed!
exited 255 after 1.78 seconds
This is due to a scoping problem: two different uses of the name "msg"
collide. So rename one of them.
Differential Revision: https://phab.mercurial-scm.org/D12427
author | Valentin Gatien-Baron <vgatien-baron@janestreet.com> |
---|---|
date | Fri, 01 Apr 2022 12:46:58 -0400 |
parents | 95c4cca641f6 |
children | 55c6ebd11cb9 |
line wrap: on
line source
Tests that the exit code is as expected when ui.detailed-exit-code is *not* enabled. $ cat >> $HGRCPATH << EOF > [ui] > detailed-exit-code=no > EOF $ hg init $ echo a > a Expect exit code 0 on success $ hg ci -Aqm initial $ hg co nonexistent abort: unknown revision 'nonexistent' [255] $ hg co 'none()' abort: empty revision set [255] $ hg co 'invalid(' hg: parse error at 8: not a prefix: end (invalid( ^ here) [255] $ hg co 'invalid(' hg: parse error at 8: not a prefix: end (invalid( ^ here) [255] $ hg continue abort: no operation in progress [255] $ hg st --config a=b abort: malformed --config option: 'a=b' (use --config section.name=value) [255] $ echo b > a $ hg ci -m second $ echo c > a $ hg ci -m third $ hg --config extensions.rebase= rebase -r . -d 0 -q warning: conflicts while merging a! (edit, then use 'hg resolve --mark') unresolved conflicts (see 'hg resolve', then 'hg rebase --continue') [1]