phases: use revision number in analyze_remote_phases Same logic as the previous change to `new_heads`, see rationnal there. This avoids a small number of `nodes -> revs` conversion speeding thing up in the 100 milliseconds order of magnitude for the worses cases. However, the rest of the logic is noisy enough that it hardly matters for now.

     1

#require cargo test-repo

     2

  $ . "$TESTDIR/helpers-testrepo.sh"

     3

  $ cd "$TESTDIR"/../rust

     4

     5

Check if Cargo.lock is up-to-date. Will fail with a 101 error code if not.

     6

     7

  $ cargo check --locked --all --quiet

     8

     9

However most CIs will run `cargo build` or similar before running the tests, so we need to check if it was modified

    10

    11

  $ testrepohg diff Cargo.lock