[Nix-dev] Hydra.nixos.org: new EPERM errors
Hi Eelco & Rob! (or who else co-maintains the build farm) Recently I see new EPERM errors in check-phases of some packages on staging, and apparently the problems aren't "caused" by any nixpkgs commits but by the build slaves themselves, perhaps some change in the way nix sets up chroots in there. I could never reproduce the problems locally (I don't run very new nix-daemon), but on Hydra they seem to always happen. Any idea about what exactly causes them? It might be best to resolve that nix setting instead of tweaking tests of individual packages... Examples: http://hydra.nixos.org/job/nixpkgs/staging/go_bootstrap.x86_64-linux http://hydra.nixos.org/job/nixpkgs/staging/libuv.x86_64-linux --Vladimir smime.p7s Description: S/MIME Cryptographic Signature ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Hydra.nixos.org: new EPERM errors
Hi, On 12/11/2016 01:21 PM, Vladimír Čunát wrote: > Recently I see new EPERM errors in check-phases of some packages on > staging, and apparently the problems aren't "caused" by any nixpkgs > commits but by the build slaves themselves, perhaps some change in the > way nix sets up chroots in there. This is caused by a Nix upgrade on the build farm machines. Builds now run in a user namespace, which confuses some of them. I've applied aszlig's seccomp patch (https://github.com/NixOS/nix/pull/1131) which fixes some problems (like the go build). > http://hydra.nixos.org/job/nixpkgs/staging/libuv.x86_64-linux This one seems to be confused by setuid/setgid not working as expected, which is hard to avoid in a user namespace with only one uid... -- Eelco Dolstra | LogicBlox, Inc. | http://nixos.org/~eelco/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Hydra.nixos.org: new EPERM errors
py.test is failing and blocking nixpkgs channel update: http://hydra.nixos.org/build/44860405/nixlog/9/raw On Thu, Dec 15, 2016 at 3:46 PM, Eelco Dolstra wrote: > Hi, > > On 12/11/2016 01:21 PM, Vladimír Čunát wrote: > > > Recently I see new EPERM errors in check-phases of some packages on > > staging, and apparently the problems aren't "caused" by any nixpkgs > > commits but by the build slaves themselves, perhaps some change in the > > way nix sets up chroots in there. > > This is caused by a Nix upgrade on the build farm machines. Builds now run > in a > user namespace, which confuses some of them. I've applied aszlig's seccomp > patch > (https://github.com/NixOS/nix/pull/1131) which fixes some problems (like > the go > build). > > > http://hydra.nixos.org/job/nixpkgs/staging/libuv.x86_64-linux > > This one seems to be confused by setuid/setgid not working as expected, > which is > hard to avoid in a user namespace with only one uid... > > -- > Eelco Dolstra | LogicBlox, Inc. | http://nixos.org/~eelco/ > ___ > nix-dev mailing list > nix-dev@lists.science.uu.nl > http://lists.science.uu.nl/mailman/listinfo/nix-dev > ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev