upstream/mercurial-mirror Files · tests/test-cache-abuse.t

filemerge: add internal merge tool to dump files forcibly...

filemerge: add internal merge tool to dump files forcibly Internal merge tool :dump implies premerge. Therefore, files aren't dumped, if premerge runs successfully. This undocumented behavior might confuse users, if they want to always dump files. But just making :dump omit premerge might cause backward compatibility issue for existing automation. This patch adds new internal merge tool :forcedump, which works as same as :dump, but omits premerge always. Internal tools annotated with "nomerge" should merge "change and delete" correctly, but _forcedump() can't. Therefore, it is annotated with "mergeonly" to always omit premerge, even though it doesn't merge files actually. This patch also adds explanation about premerge to :dump, to clarify how :dump actually works. BTW, this patch specifies internal tools with "internal:" prefix in newly added test scenario in test-merge-tools.t, even though this prefix is already deprecated. This is only for similarity to other tests in test-merge-tools.t.

Danek Duvall - - Load All Authors

File last commit:

r29255:b0b85d86 stable


                r32255:7e35d31b

default

Download file

             test-cache-abuse.t
        
                    100 lines
            
             | 2.4 KiB
            
                | text/troff
            
             |
                Tads3Lexer
            
             / tests / test-cache-abuse.t
          
                    History
                
                 |
                  Annotation
                 | Raw
                 |Copy content
                 |Copy permalink

      Enable obsolete markers

        $ cat >> $HGRCPATH << EOF

        > [experimental]

        > evolution=createmarkers

        > [phases]

        > publish=False

        > EOF

      Build a repo with some cacheable bits:

        $ hg init a

        $ cd a

        $ echo a > a

        $ hg ci -qAm0

        $ hg tag t1

        $ hg book -i bk1

        $ hg branch -q b2

        $ hg ci -Am1

        $ hg tag t2

        $ echo dumb > dumb

        $ hg ci -qAmdumb

        $ hg debugobsolete b1174d11b69e63cb0c5726621a43c859f0858d7f

        $ hg phase -pr t1

        $ hg phase -fsr t2

      Make a helper function to check cache damage invariants:

      - command output shouldn't change

      - cache should be present after first use

      - corruption/repair should be silent (no exceptions or warnings)

      - cache should survive deletion, overwrite, and append

      - unreadable / unwriteable caches should be ignored

      - cache should be rebuilt after corruption

        $ damage() {

        >  CMD=$1

        >  CACHE=.hg/cache/$2

        >  CLEAN=$3

        >  hg $CMD > before

        >  test -f $CACHE || echo "not present"

        >  echo bad > $CACHE

        >  test -z "$CLEAN" || $CLEAN

        >  hg $CMD > after

        >  diff -u before after || echo "*** overwrite corruption"

        >  echo corruption >> $CACHE

        >  test -z "$CLEAN" || $CLEAN

        >  hg $CMD > after

        >  diff -u before after || echo "*** append corruption"

        >  rm $CACHE

        >  mkdir $CACHE

        >  test -z "$CLEAN" || $CLEAN

        >  hg $CMD > after

        >  diff -u before after || echo "*** read-only corruption"

        >  test -d $CACHE || echo "*** directory clobbered"

        >  rmdir $CACHE

        >  test -z "$CLEAN" || $CLEAN

        >  hg $CMD > after

        >  diff -u before after || echo "*** missing corruption"

        >  test -f $CACHE || echo "not rebuilt"

        > }

      Beat up tags caches:

        $ damage "tags --hidden" tags2

        $ damage tags tags2-visible

        $ damage "tag -f t3" hgtagsfnodes1

      Beat up hidden cache:

        $ damage log hidden

      Beat up branch caches:

        $ damage branches branch2-base "rm .hg/cache/branch2-[vs]*"

        $ damage branches branch2-served "rm .hg/cache/branch2-[bv]*"

        $ damage branches branch2-visible

        $ damage "log -r branch(.)" rbc-names-v1

        $ damage "log -r branch(default)" rbc-names-v1

        $ damage "log -r branch(b2)" rbc-revs-v1

      We currently can't detect an rbc cache with unknown names:

        $ damage "log -qr branch(b2)" rbc-names-v1

        --- before	* (glob)

        +++ after	* (glob)

        @@ -1,8 +?,0 @@ (glob)

        -2:5fb7d38b9dc4

        -3:60b597ffdafa

        -4:b1174d11b69e

        -5:6354685872c0

        -6:5ebc725f1bef

        -7:7b76eec2f273

        -8:ef3428d9d644

        -9:ba7a936bc03c

        *** append corruption

	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

				Enable obsolete markers

				$ cat >> $HGRCPATH << EOF
				> [experimental]
				> evolution=createmarkers
				> [phases]
				> publish=False
				> EOF

				Build a repo with some cacheable bits:

				$ hg init a
				$ cd a

				$ echo a > a
				$ hg ci -qAm0
				$ hg tag t1
				$ hg book -i bk1

				$ hg branch -q b2
				$ hg ci -Am1
				$ hg tag t2

				$ echo dumb > dumb
				$ hg ci -qAmdumb
				$ hg debugobsolete b1174d11b69e63cb0c5726621a43c859f0858d7f

				$ hg phase -pr t1
				$ hg phase -fsr t2

				Make a helper function to check cache damage invariants:

				- command output shouldn't change
				- cache should be present after first use
				- corruption/repair should be silent (no exceptions or warnings)
				- cache should survive deletion, overwrite, and append
				- unreadable / unwriteable caches should be ignored
				- cache should be rebuilt after corruption

				$ damage() {
				> CMD=$1
				> CACHE=.hg/cache/$2
				> CLEAN=$3
				> hg $CMD > before
				> test -f $CACHE \|\| echo "not present"
				> echo bad > $CACHE
				> test -z "$CLEAN" \|\| $CLEAN
				> hg $CMD > after
				> diff -u before after \|\| echo "*** overwrite corruption"
				> echo corruption >> $CACHE
				> test -z "$CLEAN" \|\| $CLEAN
				> hg $CMD > after
				> diff -u before after \|\| echo "*** append corruption"
				> rm $CACHE
				> mkdir $CACHE
				> test -z "$CLEAN" \|\| $CLEAN
				> hg $CMD > after
				> diff -u before after \|\| echo "*** read-only corruption"
				> test -d $CACHE \|\| echo "*** directory clobbered"
				> rmdir $CACHE
				> test -z "$CLEAN" \|\| $CLEAN
				> hg $CMD > after
				> diff -u before after \|\| echo "*** missing corruption"
				> test -f $CACHE \|\| echo "not rebuilt"
				> }

				Beat up tags caches:

				$ damage "tags --hidden" tags2
				$ damage tags tags2-visible
				$ damage "tag -f t3" hgtagsfnodes1

				Beat up hidden cache:

				$ damage log hidden

				Beat up branch caches:

				$ damage branches branch2-base "rm .hg/cache/branch2-[vs]*"
				$ damage branches branch2-served "rm .hg/cache/branch2-[bv]*"
				$ damage branches branch2-visible
				$ damage "log -r branch(.)" rbc-names-v1
				$ damage "log -r branch(default)" rbc-names-v1
				$ damage "log -r branch(b2)" rbc-revs-v1

				We currently can't detect an rbc cache with unknown names:

				$ damage "log -qr branch(b2)" rbc-names-v1
				--- before * (glob)
				+++ after * (glob)
				@@ -1,8 +?,0 @@ (glob)
				-2:5fb7d38b9dc4
				-3:60b597ffdafa
				-4:b1174d11b69e
				-5:6354685872c0
				-6:5ebc725f1bef
				-7:7b76eec2f273
				-8:ef3428d9d644
				-9:ba7a936bc03c
				*** append corruption