-
Notifications
You must be signed in to change notification settings - Fork 112
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.
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
Nixpkgs: Try 20.03 #1266
Nixpkgs: Try 20.03 #1266
Conversation
still only beta, but to check problems early.
In terms of gas, no changes are observed in 2 tests. |
No longer stuck on https://dfinity.atlassian.net/browse/OPS-17. Now stuck on something else (not https://dfinity.atlassian.net/browse/OPS-18, I believe, despite what is said in OPS-17), related to buidling non-dfinity stuff on darwin. |
TIL that that repo is obsolete, and all its branchs are also in `nixpkgs`
Looks like this works now. |
|
|
The hydra results seem bizarre, not sure how to fix... :-( Might be related to NixOS/nixpkgs#82640, OTOH Linux also has similar logs... |
Probably because you got the derivation from the nix cache?
This bug was filed because I reported the problem that we have to @basvandijk. But I think we have a different problem, because we get
which is a different error message than NixOS/nixpkgs#82640 reports. Just filed https://dfinity.atlassian.net/browse/OPS-44 to keep this on the Infra team’s radar. |
9ac8de6 points to your own nixpkgs fork. Is there a PR against upstream already? And doesn’t that mean we’ll be tied to nixpkgs master again, and not the stable release (unless your change will be backported of course) |
Yes, that piece ( Ahhh, maybe that doesn't contain |
Just bumped |
I guess this can go in now, if someone approves. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
@Mergifyio refresh |
Command |
still only beta, but to check problems early.