In reply to @trofi:matrix.org
Built file locally for me: https://bpa.st/raw/SI6ZU. What log do you get with $ nix build --no-link github:NixOS/nixpkgs/9af373a61647257d16ae6062cddaa9094d24920c#pkgsCross.riscv64.libtool?

In reply to @p14:matrix.org
On aarch64-linux, pkgsCross.musl64.pkgsStatic.stdenv stopped being a cache hit sometime around the 26th of May. Sha eb5cd54d0 looks to be the first commit at which it is missing on the nixos-23.05 branch, but the non cross stdenv also broke/stopped being a cache hit then by the looks of things.
Does anyone have any idea why it might have gone missing and can we bring it back… ?
I would also like to have the equivalent, but from x86 to aarch64 cross.

Have you tried building it yourself or looking at the job status on Hydra?

Usually, cache misses imply a failed build.

In reply to @alex:tunstall.xyz

Have you tried building it yourself or looking at the job status on Hydra?

Usually, cache misses imply a failed build.

In reply to @p14:matrix.org
So it does look like it builds but is missing for some other reason. What bit of the hydra infrastructure would cause it to become a cache hit ordinarily?

A successful build. Everything Hydra builds is cached.

So either Hydra lost the need to build it to build its jobs (due to job changes or failed evaluation), or your local build of the package doesn't have the same derivation as that built by Hydra.

In reply to @p14:matrix.org
I’m only building nixpkgs unmodified from upstream, No overlays or anything like that. I’m wondering if hydra stopped needing to build it? How would I tell what pulled it into the hydra build when it was working, and then look for that in today’s state?