rust-lang
fix(fingerprint): explicit reason rather than "stale; unknown reason"
What does this PR try to resolve?
This was discovered during playing with rmeta reuse between cargo-check and cargo-build.
An rmeta mtime failure is basically the same as "failed to read metadata".
While we don't report in tracing log, that should be fine because dirty reason will be reported in the other place.
How to test and review this PR?
Should have no real user-facing behavior change.
r? @ehuss
rustbot has assigned @ehuss. They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.
Use r? to explicitly pick a reviewer
https://github.com/rust-lang/cargo/actions/runs/15396140671/job/43317289386#step:13:4554
Network glitch?
> [internal] load metadata for docker.io/library/alpine:3.22:
------
Dockerfile:1
--------------------
1 | >>> FROM alpine:3.22
2 |
3 | RUN apk add --no-cache openssh git
--------------------
ERROR: failed to solve: alpine:3.22: failed to resolve source metadata for docker.io/library/alpine:3.22: failed to authorize: failed to fetch oauth token: unexpected status from POST request to https://auth.docker.io/token: 500 Internal Server Error
Going to re-queue