##// END OF EJS Templates
run-tests: mechanism to report exceptions during test execution...
run-tests: mechanism to report exceptions during test execution Sometimes when running tests you introduce a ton of exceptions. The most extreme example of this is running Mercurial with Python 3, which currently spews thousands of exceptions when running the test harness. This commit adds an opt-in feature to run-tests.py to aggregate exceptions encountered by `hg` when running tests. When --exceptions is used, the test harness enables the "logexceptions" extension in the test environment. This extension wraps the Mercurial function to handle exceptions and writes information about the exception to a random filename in a directory defined by the test harness via an environment variable. At the end of the test harness, these files are parsed, aggregated, and a list of all unique Mercurial frames triggering exceptions is printed in order of frequency. This feature is intended to aid Python 3 development. I've only really tested it on Python 3. There is no shortage of improvements that could be made. e.g. we could write a separate file containing the exception report - maybe even an HTML report. We also don't capture which tests demonstrate the exceptions, so there's no turnkey way to test whether a code change made an exception disappear. Perfect is the enemy of good. I think the current patch is useful enough to land. Whoever uses it can send patches to imprve its usefulness. Differential Revision: https://phab.mercurial-scm.org/D1477

File last commit:

r22046:7a9cbb31 default
r35191:bd8875b6 default
Show More
test-update-issue1456.t
45 lines | 858 B | text/troff | Tads3Lexer
/ tests / test-update-issue1456.t
Matt Mackall
tests: replace exit 80 with #require
r22046 #require execbit
Mads Kiilerich
tests: use 'hghave execbit' for tests that manipulate x bit in file system
r15442
Adrian Buehlmann
combine tests
r12279 $ rm -rf a
$ hg init a
$ cd a
$ echo foo > foo
$ hg ci -qAm0
Siddharth Agarwal
manifestmerge: handle workdir removed, remote removed with flags...
r18895 $ echo toremove > toremove
$ echo todelete > todelete
$ chmod +x foo toremove todelete
$ hg ci -qAm1
Test that local removed/deleted, remote removed works with flags
$ hg rm toremove
$ rm todelete
Adrian Buehlmann
combine tests
r12279 $ hg co -q 0
Siddharth Agarwal
manifestmerge: handle workdir removed, remote removed with flags...
r18895
Adrian Buehlmann
combine tests
r12279 $ echo dirty > foo
$ hg up -c
Siddharth Agarwal
update: standardize error message for dirty update --check...
r19801 abort: uncommitted changes
Matt Mackall
tests: add exit codes to unified tests
r12316 [255]
Adrian Buehlmann
combine tests
r12279 $ hg up -q
$ cat foo
dirty
$ hg st -A
M foo
Siddharth Agarwal
manifestmerge: handle workdir removed, remote removed with flags...
r18895 C todelete
C toremove
Adrian Buehlmann
combine tests
r12279
Validate update of standalone execute bit change:
$ hg up -C 0
Siddharth Agarwal
manifestmerge: handle workdir removed, remote removed with flags...
r18895 1 files updated, 0 files merged, 2 files removed, 0 files unresolved
Adrian Buehlmann
combine tests
r12279 $ chmod -x foo
$ hg ci -m removeexec
nothing changed
Matt Mackall
tests: add exit codes to unified tests
r12316 [1]
Adrian Buehlmann
combine tests
r12279 $ hg up -C 0
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
$ hg up
Siddharth Agarwal
manifestmerge: handle workdir removed, remote removed with flags...
r18895 3 files updated, 0 files merged, 0 files removed, 0 files unresolved
Adrian Buehlmann
combine tests
r12279 $ hg st
Mads Kiilerich
tests: add missing trailing 'cd ..'...
r16913 $ cd ..