upstream/mercurial-mirror Files · tests/test-check-cargo-lock.t

pyoxidizer: update to PyOxidizer 0.9...

pyoxidizer: update to PyOxidizer 0.9 We were previously using a Git commit from a few days before the 0.8 release. This commit upgrades us to the just-released 0.9 release. This required some Starlark changes due to backwards incompatible changes. Differential Revision: https://phab.mercurial-scm.org/D9228

Raphaël Gomès - - Load All Authors

File last commit:

r46231:ba0d93a5 default


                r46341:f95b1679

stable

Download file

             test-check-cargo-lock.t
        
                    11 lines
            
             | 353 B
            
                | text/troff
            
             |
                Tads3Lexer
            
             / tests / test-check-cargo-lock.t
          
                    History
                
                 |
                  Annotation
                 | Raw
                 |Copy content
                 |Copy permalink

      #require cargo test-repo

        $ . "$TESTDIR/helpers-testrepo.sh"

        $ cd "$TESTDIR"/../rust

      Check if Cargo.lock is up-to-date. Will fail with a 101 error code if not.

        $ cargo check --locked --all --quiet

      However most CIs will run `cargo build` or similar before running the tests, so we need to check if it was modified

        $ testrepohg diff Cargo.lock

	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

				#require cargo test-repo
				$ . "$TESTDIR/helpers-testrepo.sh"
				$ cd "$TESTDIR"/../rust

				Check if Cargo.lock is up-to-date. Will fail with a 101 error code if not.

				$ cargo check --locked --all --quiet

				However most CIs will run `cargo build` or similar before running the tests, so we need to check if it was modified

				$ testrepohg diff Cargo.lock