upstream/mercurial-mirror Files · tests/helpers-testrepo.sh

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

Yuya Nishihara - - Load All Authors

File last commit:

r33201:45d6e276 default


                r35191:bd8875b6

default

Download file

             helpers-testrepo.sh
        
                    53 lines
            
             | 1.7 KiB
            
                | application/x-sh
            
             |
                BashLexer
            
             / tests / helpers-testrepo.sh
          
                    History
                
                 |
                  Annotation
                 | Raw
                 |Copy content
                 |Copy permalink

      # In most cases, the mercurial repository can be read by the bundled hg, but

      # that isn't always true because third-party extensions may change the store

      # format, for example. In which case, the system hg installation is used.

      #

      # We want to use the hg version being tested when interacting with the test

      # repository, and the system hg when interacting with the mercurial source code

      # repository.

      #

      # The mercurial source repository was typically orignally cloned with the

      # system mercurial installation, and may require extensions or settings from

      # the system installation.

      syshg () {

          (

              syshgenv

              exec hg "$@"

          )

      }

      # Revert the environment so that running "hg" runs the system hg

      # rather than the test hg installation.

      syshgenv () {

          . "$HGTEST_RESTOREENV"

          HGPLAIN=1

          export HGPLAIN

      }

      # The test-repo is a live hg repository which may have evolution markers

      # created, e.g. when a ~/.hgrc enabled evolution.

      #

      # Tests may be run using a custom HGRCPATH, which do not enable evolution

      # markers by default.

      #

      # If test-repo includes evolution markers, and we do not enable evolution

      # markers, hg will occasionally complain when it notices them, which disrupts

      # tests resulting in sporadic failures.

      #

      # Since we aren't performing any write operations on the test-repo, there's

      # no harm in telling hg that we support evolution markers, which is what the

      # following lines for the hgrc file do:

      cat >> "$HGRCPATH" << EOF

      [experimental]

      evolution = createmarkers

      EOF

      # Use the system hg command if the bundled hg can't read the repository with

      # no warning nor error.

      if [ -n "`hg id -R "$TESTDIR/.." 2>&1 >/dev/null`" ]; then

          alias testrepohg=syshg

          alias testrepohgenv=syshgenv

      else

          alias testrepohg=hg

          alias testrepohgenv=:

      fi

	Site-wide shortcuts
/	Use quick search box
g h	Goto home page
g g	Goto my private gists page
g G	Goto my public gists page
g 0-9	Goto bookmarked items from 0-9
n r	New repository page
n g	New gist page

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository access permissions settings
t s	Toggle sidebar on some pages

				# In most cases, the mercurial repository can be read by the bundled hg, but
				# that isn't always true because third-party extensions may change the store
				# format, for example. In which case, the system hg installation is used.
				#
				# We want to use the hg version being tested when interacting with the test
				# repository, and the system hg when interacting with the mercurial source code
				# repository.
				#
				# The mercurial source repository was typically orignally cloned with the
				# system mercurial installation, and may require extensions or settings from
				# the system installation.
				syshg () {
				(
				syshgenv
				exec hg "$@"
				)
				}

				# Revert the environment so that running "hg" runs the system hg
				# rather than the test hg installation.
				syshgenv () {
				. "$HGTEST_RESTOREENV"
				HGPLAIN=1
				export HGPLAIN
				}

				# The test-repo is a live hg repository which may have evolution markers
				# created, e.g. when a ~/.hgrc enabled evolution.
				#
				# Tests may be run using a custom HGRCPATH, which do not enable evolution
				# markers by default.
				#
				# If test-repo includes evolution markers, and we do not enable evolution
				# markers, hg will occasionally complain when it notices them, which disrupts
				# tests resulting in sporadic failures.
				#
				# Since we aren't performing any write operations on the test-repo, there's
				# no harm in telling hg that we support evolution markers, which is what the
				# following lines for the hgrc file do:
				cat >> "$HGRCPATH" << EOF
				[experimental]
				evolution = createmarkers
				EOF

				# Use the system hg command if the bundled hg can't read the repository with
				# no warning nor error.
				if [ -n "`hg id -R "$TESTDIR/.." 2>&1 >/dev/null`" ]; then
				alias testrepohg=syshg
				alias testrepohgenv=syshgenv
				else
				alias testrepohg=hg
				alias testrepohgenv=:
				fi