Closed aaronpkelly closed 1 year ago
It just looks like Nix is rebuilding nodejs, which would definitely take some time and make some noise. Hard to say why it's not just substituting it from the binary cache without seeing your config.
Yeah I don't know why nodejs
is not using the binary cache
Even when trying to just start a shell with nodejs
, it still attempts to build it:
$ nix-shell -p nodejs
these derivations will be built:
/nix/store/gxr007lvkx23j75pdp94pr44ivgrwyy3-nodejs-18.15.0.drv
I think this may be a general nix problem and not a home-manager problem, so I'll open a ticket over there
Do you maybe have an overlay in your nixpkgs config that could be causing the rebuild?
I would suggest cloning nixpkgs, checking out the revision you're supposed to be on (85b081528b9), running nix-instantiate -A nodejs
and then comparing the two .drv
files using nix-diff
to see what's different.
Are you following the right branch?
Is there an existing issue for this?
Issue description
My home-manager seems to be stuck in an infinite loop of trying to compile nodejs-18.15.0.drv
I normally just use
home-manager switch
and it works fine, but this is the first time home-manager has been stuck on something "for a long time".So, for making this issue, I used
home-manager switch --debug --print-build-logs --show-trace --verbose
so that I could try and see where it's getting stuck, and here it is:At this point my fan whirs up... that's the way it stays for hours. The above process never finishes.
I used htop to find out what processes are being run in the background, and I can see that there are a number of
cc1plus
processes running over-and-over. They exist for about 10 seconds, and then new ones as created.Here's an example of one:
This will continue for hours, the same cc1plus process attempting to build what looks like the same file over and over.
Any idea how I can get past this?
Maintainer CC
No response
System information