view tests/test-check-cargo-lock.t @ 49862:b1147450c55c

sparse: fix a py2 based usage of `map()`

In a local pytype run, this fixes:

    File "/mnt/c/Users/Matt/hg/hgext/sparse.py", line 386, in debugsparse:
        unsupported operand type(s) for item retrieval: 'fcounts: Iterator[int]' and '0: int' [unsupported-operands]
      No attribute '__getitem__' on 'fcounts: Iterator[int]'
    File "/mnt/c/Users/Matt/hg/hgext/sparse.py", line 387, in debugsparse:
        unsupported operand type(s) for item retrieval: 'fcounts: Iterator[int]' and '1: int' [unsupported-operands]
      No attribute '__getitem__' on 'fcounts: Iterator[int]'
    File "/mnt/c/Users/Matt/hg/hgext/sparse.py", line 388, in debugsparse:
        unsupported operand type(s) for item retrieval: 'fcounts: Iterator[int]' and '2: int' [unsupported-operands]
      No attribute '__getitem__' on 'fcounts: Iterator[int]'

#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