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
nixUnstable: pre20201205_a5d85d0 -> pre20210219_548437c #109309
Conversation
Last time I checked the current Also, this should be backported IMHO. |
0c7ad46
to
f86df1a
Compare
updating hydra to latest, then picking what the flake.lock is locked to |
f86df1a
to
e74a032
Compare
|
@GrahamcOfBorg build hydra-unstable |
This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch) Result of 3 packages marked as broken and skipped:
51 packages failed to build and are new build failures:
|
gah, darwin :( |
It is already broken now and I think some tests are failing. We should fix it eventually. |
Yea, but the current darwin build is passing https://hydra.nixos.org/build/135058690 so I don't want to break darwin users. Especially since this should be backported. Wish darwin wasn't so expensive to get CI for. (Free for linux) |
looks like NixOS/nix@86a2cee was merged which would allow me to revert gcc version pinning |
if we can't merge this because of darwin yet, we should at least apply the patch from NixOS/nix#4470. |
0802e72
to
7deeb4a
Compare
reverted the gcc9 change, because it's no longer relevant, may also fix the darwin build added the related flake inputs changes which I cared about and attempted to open this PR in the first place @SuperSandro2000 do you mind doing a darwin review? |
|
This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch). Result of 4 packages failed to build and are new build failures:
Not sure if this is related to the sandbox or not. Edit: it is not. |
This comment has been minimized.
This comment has been minimized.
This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch). Result of 1 package marked as broken and skipped:
2 packages blacklisted:
2 packages failed to build and are new build failures:
53 packages built:
|
I think that failure has been a long time flakey issue can you try to build it again? |
Can confirm. I regularly compile Nix on my own since I have a few patches on top and this is one of the tests that fail from time to time. |
I have build it at least two times with that issue. |
I had another coworker be able to build it fine. I might just merge and babysit, restarting it. |
174b31c
to
feb95d9
Compare
Don't have the capacity to test (tonight at least in my tz), but LGTM 👍 |
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.
@jonringer LGTM, can be merged from my PoV 👍
@ofborg eval |
This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch). Result of 1 package marked as broken and skipped:
2 packages blacklisted:
3 packages failed to build and already failed to build on hydra master:
50 packages built:
|
This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch). Result of 5 packages failed to build and already failed to build on hydra master:
1 package failed to build and are new build failure:
The following issues got detected with the above build packages.
nix-direnv:
warning: unused-argument
warning: EvalError |
nixUnstable is now past this. |
closing due to other PR |
Motivation for this change
update nixUnstable
had to pin gcc to gcc9 as additional work was merged since the last update which is not compatible. Pragmatically, we can bump to gcc10 when upstream has CI around gcc10Using the version of nixUnstable which hydra is using. and just picked the patches that I really want to use.
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)