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

smartset: use native set operations as fast paths...

smartset: use native set operations as fast paths For set operations like "&" and "-", where we know both basesets have their sets ready, and the first set is sorted, use the native Python set operations as a fast path. Note: "+" is not optimized as that will break the ordering. This leads to noticeable improvements on performance: revset | before | after | delta ---------------------------------------------------------------- draft() & draft() & draft() & draft() | 776 | 477 | -39% draft() + draft() + draft() + draft() | 2849 | 2864 | draft() - draft() + draft() - draft() | 943 | 240 | -75% draft() - draft() - draft() - draft() | 557 | 197 | -64% (time measured in microseconds)

timeless - - Load All Authors

File last commit:

r29219:3c9066ed default


                r31020:2d1bf840

default

Download file

             helpers-testrepo.sh
        
                    19 lines
            
             | 678 B
            
                | application/x-sh
            
             |
                BashLexer
            
             / tests / helpers-testrepo.sh
          
                    History
                
                 |
                  Annotation
                 | Raw
                 |Copy content
                 |Copy permalink

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

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

      #

      # Tests are 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

	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

				# The test-repo is a live hg repository which may have evolution
				# markers created, e.g. when a ~/.hgrc enabled evolution.
				#
				# Tests are 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