Hi, our Hydra exploded today: after a recent change to our nixpkgs branch, we encountered the evaluator consuming infinite CPU and quite a lot of memory.
Updating to a current version of Hydra (nixpkgs trunk) didn’t help. We’re going to go through the changes that caused this tomorrow. However, I wanted to check whether anybody has experienced this before and might know what can trigger this behaviour. I also haven’t seen any changes in the last year to hydra that would seem relevant, apart from, maybe, the concurrent evaluator, which isn’t in nixpkgs master yet. Christian -- Christian Theune · [email protected] · +49 345 219401 0 Flying Circus Internet Operations GmbH · http://flyingcircus.io Forsterstraße 29 · 06112 Halle (Saale) · Deutschland HR Stendal HRB 21169 · Geschäftsführer: Christian. Theune, Christian. Zagrodnick
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ nix-dev mailing list [email protected] http://lists.science.uu.nl/mailman/listinfo/nix-dev
