Add cachix as a blocker for channel updates #77311
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/cant-build-cachix-0-3-4/5390/2 |
|
@domenkozar There is also this list that @peti maintains. Maybe cachix should be added here as well? https://github.com/peti/ci/blob/master/haskell-nixpkgs.nix Although I don't know exactly what effect the above list has. |
ofborg
bot
added
10.rebuild-darwin: 0
3 tasks
|
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cachix broke quite a few times in last year and it's really hard to keep up with that. Getting lots of support request (for example see https://discourse.nixos.org/t/cant-build-cachix-0-3-4/5390).
I hope this makes sense since it's a widely used service within community. I'm happy to be pinged when it does break, but I'd like for that to happen before users see the breakage, which is what release critical jobs are for.