Files modified in the past should not trigger a fingerprint change
Files modified in the past should not trigger a fingerprint change

Previously, we would bail from the fingerprint computation if the old
and new mtimes had changed in *any* way. This caused some issues of
rebuilding with filesystems that do not preserve nanosecond
granularity (#2874).

durka/cargo,durka/cargo,achanda/cargo,tsurai/cargo,eminence/cargo,vojtechkral/cargo,sbeckeriv/cargo,AndiDog/cargo,sbeckeriv/cargo,tshepang/cargo,achanda/cargo,nipunn1313/cargo,rustyhorde/cargo,nipunn1313/cargo,rust-lang/cargo,vojtechkral/cargo,tshepang/cargo,tsurai/cargo,AndiDog/cargo,rustyhorde/cargo,tsurai/cargo,vojtechkral/cargo,achanda/cargo,rust-lang/cargo,tsurai/cargo,tsurai/cargo,eminence/cargo,eminence/cargo,nipunn1313/cargo,eminence/cargo,nipunn1313/cargo,rust-lang/cargo,tshepang/cargo,tshepang/cargo,AndiDog/cargo,sbeckeriv/cargo,achanda/cargo,vojtechkral/cargo,rust-lang/cargo,rustyhorde/cargo,durka/cargo,sbeckeriv/cargo,rustyhorde/cargo,AndiDog/cargo,durka/cargo,AndiDog/cargo