view tests/test-check-cargo-lock.t @ 46325:e5e6282fa66a

hghave: split apart testing for the curses module and `tic` executable

ef771d329961 skipped the check for the `tic` executable, because the curses
module alone on Windows is enough to pass the `test-*-curses.t` tests.  However,
`test-status-color.t` uses this same check and explicitly invoked the
executable, which fails on Windows.  From the cursory searching I did, curses on
unix requires `tic`, which I assume is why they were tied together in the first
place.  So this continues to require both to get past the curses guards on non
Windows platforms.

Differential Revision: https://phab.mercurial-scm.org/D9814

#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