upstream/mercurial-mirror Files · tests/test-status-eacces.t

run-tests: bump the default timeout on Windows to 4x the normal value...

run-tests: bump the default timeout on Windows to 4x the normal value There are a ridiculous number of tests that timeout on Windows with the 360 sec default (~60). And because of the bug where timed out tests still run to completion before the results are thrown away[1], the timeout does nothing but waste time, so there's no reason to try to find a lower value that still works. For reference on my system: # Ran 909 tests, 116 skipped, 119 failed. python hash seed: 2052473208 real 151m44.322s user 0m0.077s sys 0m0.046s [1] I thought that I wrote a bug for this, but search isn't finding it.

Arseniy Alekseyev - - Load All Authors

File last commit:

r51218:86d2a28c stable


                r52845:f4c03808

default

Download file

             test-status-eacces.t
        
                    45 lines
            
             | 751 B
            
                | text/troff
            
             |
                Tads3Lexer
            
             / tests / test-status-eacces.t
          
                    History
                
                 |
                  Annotation
                 | Raw
                 |Copy content
                 |Copy permalink

      #testcases dirstate-v1 dirstate-v2

      #if dirstate-v2

        $ cat >> $HGRCPATH << EOF

        > [format]

        > use-dirstate-v2=1

        > [storage]

        > dirstate-v2.slow-path=allow

        > EOF

      #endif

      The proliferation of status implementations can be confusing:

      - The pure python implementation:

      (no-rhg pure !)

      - The C implementation:

      (no-rhg no-rust no-pure !)

      - The two rust implementations:

      (rhg !)

      (no-rhg rust !)

        $ hg init repo1

        $ cd repo1

        $ mkdir d1

        $ touch d1/x

        $ hg commit -Am.

        adding d1/x

        $ touch d1/y

        $ chmod -r d1

        $ hg status

        d1: $EACCES$

        ! d1/x (rhg !)

        ! d1/x (no-rhg rust !)

        $ hg status

        d1: $EACCES$

        ! d1/x (rust !)

        ! d1/x (no-rust rhg !)

        $ chmod +r d1

        $ hg status

        ? d1/y

        $ touch d1/z

        $ hg status

        ? d1/y

        ? d1/z

	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

				#testcases dirstate-v1 dirstate-v2

				#if dirstate-v2
				$ cat >> $HGRCPATH << EOF
				> [format]
				> use-dirstate-v2=1
				> [storage]
				> dirstate-v2.slow-path=allow
				> EOF
				#endif


				The proliferation of status implementations can be confusing:
				- The pure python implementation:
				(no-rhg pure !)
				- The C implementation:
				(no-rhg no-rust no-pure !)
				- The two rust implementations:
				(rhg !)
				(no-rhg rust !)

				$ hg init repo1
				$ cd repo1
				$ mkdir d1
				$ touch d1/x
				$ hg commit -Am.
				adding d1/x
				$ touch d1/y
				$ chmod -r d1
				$ hg status
				d1: $EACCES$
				! d1/x (rhg !)
				! d1/x (no-rhg rust !)
				$ hg status
				d1: $EACCES$
				! d1/x (rust !)
				! d1/x (no-rust rhg !)
				$ chmod +r d1
				$ hg status
				? d1/y

				$ touch d1/z
				$ hg status
				? d1/y
				? d1/z