Mercurial > public > mercurial-scm > hg
diff tests/test-flagprocessor.t @ 34845:78d9a7b7cdb6
extensions: always include traceback when extension setup fails
I have spent a lot of time debugging extensions that failed to load
because we don't include a traceback and I didn't realize I could get
traceback for the extension failure with --traceback. Let's just turn
them on by default, since it should be rare that the user sees these
tracebacks anyway (and if they do, it's not so bad if the extra
traceback pushes them a little harder to report the problem).
Since we already had a test case with --traceback and one without, I
just removed the one with the flag.
Differential Revision: https://phab.mercurial-scm.org/D1164
| author | Martin von Zweigbergk <martinvonz@google.com> |
|---|---|
| date | Tue, 17 Oct 2017 10:31:44 -0700 |
| parents | eb586ed5d8ce |
| children | 4441705b7111 |
line wrap: on
line diff
--- a/tests/test-flagprocessor.t Tue Oct 17 10:25:32 2017 -0700 +++ b/tests/test-flagprocessor.t Tue Oct 17 10:31:44 2017 -0700 @@ -162,8 +162,18 @@ > duplicate=$TESTDIR/flagprocessorext.py > EOF $ hg debugrebuilddirstate + Traceback (most recent call last): + File "*/mercurial/extensions.py", line *, in _runextsetup (glob) + extsetup(ui) + File "*/tests/flagprocessorext.py", line *, in extsetup (glob) + validatehash, + File "*/mercurial/revlog.py", line *, in addflagprocessor (glob) + raise error.Abort(msg) + Abort: cannot register multiple processors on flag '0x8'. *** failed to set up extension duplicate: cannot register multiple processors on flag '0x8'. $ hg st 2>&1 | egrep 'cannot register multiple processors|flagprocessorext' + File "*/tests/flagprocessorext.py", line *, in extsetup (glob) + Abort: cannot register multiple processors on flag '0x8'. *** failed to set up extension duplicate: cannot register multiple processors on flag '0x8'. File "*/tests/flagprocessorext.py", line *, in b64decode (glob)