Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

nixos-unstable channel not advancing #120120

Closed
lukegb opened this issue Apr 21, 2021 · 2 comments
Closed

nixos-unstable channel not advancing #120120

lukegb opened this issue Apr 21, 2021 · 2 comments
Labels
0.kind: bug 1.severity: channel blocker Blocks a channel

Comments

@lukegb
Copy link
Contributor

lukegb commented Apr 21, 2021

nixos-unstable channel is wedged and cannot advance despite successful Hydra tested builds and completed , probably due to some bug in the channel scripts, but it's not clear.

One possibility is that a Nix update caused some of the NAR list files (like https://cache.nixos.org/zqwjsgl3g77h53n6blh0khkz77b9jaaw.ls) to be corrupted, but it's not clear why this is blocking the channel from advancing.
@lukegb
Copy link
Contributor Author

lukegb commented Apr 21, 2021 

<gchristensen> update-nixos-unstable-start[1252]:  $ index-debuginfo /scratch/hydra-mirror/nixos-files.sql
<gchristensen> update-nixos-unstable-start[2007]: error (ignored): error: input compression not recognized
<gchristensen> update-nixos-unstable-start[2007]: error (ignored): error: input compression not recognized
<gchristensen> update-nixos-unstable-start[2007]: error (ignored): error: input compression not recognized
<gchristensen> update-nixos-unstable-start[2007]: error (ignored): error: input compression not recognized
<gchristensen> update-nixos-unstable-start[2007]: error: input compression not recognized
<gchristensen> update-nixos-unstable-start[1252]: Command failed with code (1) errno (0).

@lukegb lukegb mentioned this issue Apr 22, 2021
Closed
lukegb added a commit to lukegb/nix that referenced this issue Apr 22, 2021
@lukegb
libutil: allow decompression with none/empty method
97dde3c 
The S3 store relies on the ability to be able to decompress things with
an empty method, because it just passes the value of the Content-Encoding
directly to decompress.

If the file is not compressed, then this will cause the compression
routine to get confused.

This caused NixOS/nixpkgs#120120.
@lukegb lukegb mentioned this issue Apr 22, 2021
Merged
@edolstra
Copy link
Member

Closed by NixOS/infra@43851f2.

stephank pushed a commit to stephank/nix that referenced this issue Apr 23, 2021
@lukegb @stephank
libutil: allow decompression with none/empty method
c3d277b 
The S3 store relies on the ability to be able to decompress things with
an empty method, because it just passes the value of the Content-Encoding
directly to decompress.

If the file is not compressed, then this will cause the compression
routine to get confused.

This caused NixOS/nixpkgs#120120.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
0.kind: bug 1.severity: channel blocker Blocks a channel
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lukegb @edolstra