upstream/mercurial-mirror Files · tests/test-manifest.t

exchange: move disabling of rev-branch-cache bundle part out of narrow...

exchange: move disabling of rev-branch-cache bundle part out of narrow I'm attempting to refactor changegroup code in order to better support alternate storage backends. The narrow extension is performing a lot of monkeypatching to this code and it is making it difficult to reason about how everything works. I'm reasonably certain I would be unable to abstract storage without requiring extensive rework of narrow. I believe it is less effort to move narrow code into core so it can be accounted for when changegroup code is refactored. So I'll be doing that. The first part of this is integrating the disabling of the cache:rev-branch-cache bundle2 part into core. This doesn't seem like it is related to changegroup, but narrow's modifications to changegroup are invasive and also require taking its code for bundle generation and exchange into core in order for the changegroup code to work. Differential Revision: https://phab.mercurial-scm.org/D4007

Yuya Nishihara - - Load All Authors

File last commit:

r38561:ece3f2d0 default


                r38813:ab765bc4

default

Download file

             test-manifest.t
        
                    95 lines
            
             | 1.5 KiB
            
                | text/troff
            
             |
                Tads3Lexer
            
             / tests / test-manifest.t
          
                    History
                
                 |
                  Annotation
                 | Raw
                 |Copy content
                 |Copy permalink

      Source bundle was generated with the following script:

      # hg init

      # echo a > a

      # ln -s a l

      # hg ci -Ama -d'0 0'

      # mkdir b

      # echo a > b/a

      # chmod +x b/a

      # hg ci -Amb -d'1 0'

        $ hg init

        $ hg unbundle "$TESTDIR/bundles/test-manifest.hg"

        adding changesets

        adding manifests

        adding file changes

        added 2 changesets with 3 changes to 3 files

        new changesets b73562a03cfe:5bdc995175ba

        (run 'hg update' to get a working copy)

      The next call is expected to return nothing:

        $ hg manifest

        $ hg co

        3 files updated, 0 files merged, 0 files removed, 0 files unresolved

        $ hg manifest

        a

        b/a

        l

        $ hg files -vr .

                 2   a

                 2 x b/a

                 1 l l

        $ hg files -r . -X b

        a

        l

        $ hg files -T '{path} {size} {flags}\n'

        a 2 

        b/a 2 x

        l 1 l

        $ hg files -T '{path} {node|shortest}\n' -r.

        a 5bdc

        b/a 5bdc

        l 5bdc

        $ hg manifest -v

        644   a

        755 * b/a

        644 @ l

        $ hg manifest -T '{path} {rev}\n'

        a 1

        b/a 1

        l 1

        $ hg manifest --debug

        b789fdd96dc2f3bd229c1dd8eedf0fc60e2b68e3 644   a

        b789fdd96dc2f3bd229c1dd8eedf0fc60e2b68e3 755 * b/a

        047b75c6d7a3ef6a2243bd0e99f94f6ea6683597 644 @ l

        $ hg manifest -r 0

        a

        l

        $ hg manifest -r 1

        a

        b/a

        l

        $ hg manifest -r tip

        a

        b/a

        l

        $ hg manifest tip

        a

        b/a

        l

        $ hg manifest --all

        a

        b/a

        l

      The next two calls are expected to abort:

        $ hg manifest -r 2

        abort: unknown revision '2'!

        [255]

        $ hg manifest -r tip tip

        abort: please specify just one revision

        [255]

	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

				Source bundle was generated with the following script:

				# hg init
				# echo a > a
				# ln -s a l
				# hg ci -Ama -d'0 0'
				# mkdir b
				# echo a > b/a
				# chmod +x b/a
				# hg ci -Amb -d'1 0'

				$ hg init
				$ hg unbundle "$TESTDIR/bundles/test-manifest.hg"
				adding changesets
				adding manifests
				adding file changes
				added 2 changesets with 3 changes to 3 files
				new changesets b73562a03cfe:5bdc995175ba
				(run 'hg update' to get a working copy)

				The next call is expected to return nothing:

				$ hg manifest

				$ hg co
				3 files updated, 0 files merged, 0 files removed, 0 files unresolved

				$ hg manifest
				a
				b/a
				l

				$ hg files -vr .
				2 a
				2 x b/a
				1 l l
				$ hg files -r . -X b
				a
				l
				$ hg files -T '{path} {size} {flags}\n'
				a 2
				b/a 2 x
				l 1 l
				$ hg files -T '{path} {node\|shortest}\n' -r.
				a 5bdc
				b/a 5bdc
				l 5bdc

				$ hg manifest -v
				644 a
				755 * b/a
				644 @ l
				$ hg manifest -T '{path} {rev}\n'
				a 1
				b/a 1
				l 1

				$ hg manifest --debug
				b789fdd96dc2f3bd229c1dd8eedf0fc60e2b68e3 644 a
				b789fdd96dc2f3bd229c1dd8eedf0fc60e2b68e3 755 * b/a
				047b75c6d7a3ef6a2243bd0e99f94f6ea6683597 644 @ l

				$ hg manifest -r 0
				a
				l

				$ hg manifest -r 1
				a
				b/a
				l

				$ hg manifest -r tip
				a
				b/a
				l

				$ hg manifest tip
				a
				b/a
				l

				$ hg manifest --all
				a
				b/a
				l

				The next two calls are expected to abort:

				$ hg manifest -r 2
				abort: unknown revision '2'!
				[255]

				$ hg manifest -r tip tip
				abort: please specify just one revision
				[255]