hash mismatch building lenovo-x1-carbon-gen11-debug
Opened this issue · 0 comments
On building Ghaf lenovo-x1-carbon-gen11-debug we see occasional build failures:
error: builder for '/nix/store/dyw71dxaaxvgyl3mnl5xc54ryqf5kxay-nixos-disk-image.drv' failed with exit code 1;
last 10 log lines:
> copying path '/nix/store/3z537aq6rbvfrl59bgfm6ls22z2dyy8z-chromium-120.0.6099.71-sandbox' to 'local'...
> copying path '/nix/store/bblyj5b3ii8n6v4ra0nb37cmi3lf8rz9-coreutils-9.3' to 'local'...
> copying path '/nix/store/rpzk0h1d11ciarcjkv1zzgsa1iz8zmv8-libidn-1.41' to 'local'...
> error: hash mismatch importing path '/nix/store/3z537aq6rbvfrl59bgfm6ls22z2dyy8z-chromium-120.0.6099.71-sandbox';
> specified: sha256:01bffjgrkk0saf32pjrgpcx893dksp2mqcbpy8bfn6wrinndd2gs
> got: sha256:1wi876fpb69cv2n8vkzr04mv2p5hbc543mpdci7a2lvk3ghnsr2c
More examples are available from the ~'past month' lenovo-x1-carbon-gen11-debug build failures in github action pre-merge builds one can search from: https://github.com/tiiuae/ghaf/actions/workflows/build.yml?query=is%3Afailure.
The issue seems to relate to chromium build (hence only lenovo-x1-carbon-gen11-debug is impacted from the set of targets currently built in pre-merge build workflow). Having many substituters configured seems to increase the likelihood of a build hitting this issue. For instance, github actions pre-merge builds configure the following binary caches: https://github.com/tiiuae/ghaf/blob/main/.github/workflows/build.yml#L146-L147.
As a workaround @brianmcgillion temporarily disabled the lenovo-x1-carbon-gen11-debug target from the pre-merge build workflow with PR: #441.
We would like to re-enable the lenovo-x1-carbon-gen11-debug in the pre-merge build action, but this issue needs to be resolved first.