view tests/test-check-cargo-lock.t @ 49970:8d390a13474d stable

setup: make the version computation process more resistant

The tag fetching might return and empty string¹, from there everything derails
quickly. As setup tools becomes more picky about version format we make the
whole seems a bit more robust.

The resulting version will be obviously weird, but at least it will actually
install itself.

[1] This is a problem we will address in the next changesets.

#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