Mercurial > hg
view tests/test-check-cargo-lock.t @ 45784:74271829ddc0
clonebundles: move a bundle of clone bundle related code to a new module
In the process on general clone bundle automatically, we need to make some
function available more widely. This is a good opportunity to extract a
significant amount of code from `mercurial.exchange` into a new
`mercurial.bundlecaches`. This make `mercurial.exchange` move under the 3K line
range (hooray…).
The module is called `bundlecaches` because I expect it to be eventually useful
for more than just clone bundle (like pull bunbles).
Differential Revision: https://phab.mercurial-scm.org/D9208
author | Pierre-Yves David <pierre-yves.david@octobus.net> |
---|---|
date | Thu, 15 Oct 2020 15:57:36 +0200 |
parents | ba0d93a5f06f |
children |
line wrap: on
line source
#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