tests/test-check-cargo-lock.t
author Pierre-Yves David <pierre-yves.david@octobus.net>
Wed, 13 Mar 2024 12:02:06 +0100
changeset 51599 b0aaffcb6fcf
parent 45654 ba0d93a5f06f
permissions -rw-r--r--
tags-cache: directly perform a monimal walk for hgtagsfnodescache warming We do something narrower than the path retrieving data. So lets use dedicated code instead. This provides further useful speedup: ### data-env-vars.name = mozilla-try-2023-03-22-zstd-sparse-revlog # benchmark.name = hg.debug.debug-update-cache # bin-env-vars.hg.flavor = default # bin-env-vars.hg.py-re2-module = default # benchmark.variants.pre-state = warm before-this-series: 19.947581 skip-fnode-filter: 18.916804 (-5.17%, -1.03) use-rev-num: 17.493725 (-12.30%, -2.45) this-changesets: 15.919466 (-20.19%, -4.03)

#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