Re: [Nix-dev] hydra admins: please take care of i686 GHC out of memory issues
On 01/28/2014 04:15 PM, Gergely Risko wrote: Maybe it's a bit laborous to get all the transitive dependencies, so can you please just reinit gitAnnex, that's the only remaining thing I use. One-time solutions won't help for long. Things get rebuilt quite often, e.g. I think I'll soon merge x-updates where it builds currently, but it may be just the other way next time... http://hydra.nixos.org/job/nixpkgs/xorg-test/gitAndTools.gitAnnex.i686-linux Vlada 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 admins: please take care of i686 GHC out of memory issues
Hi, Thanks, you catched a lot of the dependencies, e.g. pipesParse.i686-linux is green now, but dependencies with distance >=2 have been missed, e.g.: http://hydra.nixos.org/job/nixpkgs/trunk/gitAndTools.gitAnnex.i686-linux Maybe it's a bit laborous to get all the transitive dependencies, so can you please just reinit gitAnnex, that's the only remaining thing I use. Thanks, Gergely On Tue, 28 Jan 2014 13:10:16 +0100, Rob Vermaas writes: > Hi, > > I went for the option to delete the builds from the DB. So they should > show up at the next evaluation again. > > Cheers, > Rob > > On Tue, Jan 28, 2014 at 12:19 PM, Gergely Risko wrote: >> Hi, >> >> Is it possible to make a change that only changes the libraries and >> other dependencies (e.g. git-annex)? Because by changing GHC itself we >> would trigger (most probably another failing) GHC rebuild. >> >> Gergely >> >> On Tue, 28 Jan 2014 12:02:16 +0100, Rob Vermaas >> writes: >> >>> Hi, >>> >>> that's a bit tricky, as the .drv's of the failed builds have been >>> garbage collected. We need to fix that in Hydra. For now, easiest >>> would be to add a change somewhere that'll trigger a rebuild of the >>> whole i686-linux ghc packages, or to physically delete these builds >>> from the hydra database and re-evaluate the jobsets. Not sure what is >>> best yet. >>> >>> Cheers, >>> Rob >>> >>> On Tue, Jan 28, 2014 at 11:27 AM, Gergely Risko wrote: Hi, Thanks, this looks great! But on the other hand now someone has to restart all the builds that failed because of ghc being unavailable previously, e.g.: http://hydra.nixos.org/job/nixpkgs/trunk/haskellPackages_ghc763.ghc.i686-linux http://hydra.nixos.org/job/nixpkgs/trunk/haskellPackages.pipesParse.i686-linux But there are thousands more. :( Gergely On Tue, 28 Jan 2014 10:42:01 +0100, Rob Vermaas writes: > The build should be available on hydra.nixos.org now. > > Cheers, > Rob > > On Mon, Jan 27, 2014 at 9:12 PM, Peter Simons wrote: >> Hi guys, >> >> I have a successful GHC 7.6.3 build for i686-linux available here: >> >> >> http://hydra.cryp.to/job/nixpkgs/haskell-updates/haskellPackages.ghcPlain.i686-linux >> >> If hydra.nixos.org cannot compile that package for some reason, could >> someone with appropriate admin privileges please import that closure >> from my server into the /nix store on hydra.nix.org? I believe >> >> curl >> "http://hydra.cryp.to/build/37672/nix/closure/ghc-7.6.3.closure.gz"; | >> gunzip | nix-store --import >> >> should do the trick. >> >> Rob, maybe? >> >> Take care, >> Peter >> >> ___ >> 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 >> >> ___ >> 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
Re: [Nix-dev] hydra admins: please take care of i686 GHC out of memory issues
Hi, I went for the option to delete the builds from the DB. So they should show up at the next evaluation again. Cheers, Rob On Tue, Jan 28, 2014 at 12:19 PM, Gergely Risko wrote: > Hi, > > Is it possible to make a change that only changes the libraries and > other dependencies (e.g. git-annex)? Because by changing GHC itself we > would trigger (most probably another failing) GHC rebuild. > > Gergely > > On Tue, 28 Jan 2014 12:02:16 +0100, Rob Vermaas > writes: > >> Hi, >> >> that's a bit tricky, as the .drv's of the failed builds have been >> garbage collected. We need to fix that in Hydra. For now, easiest >> would be to add a change somewhere that'll trigger a rebuild of the >> whole i686-linux ghc packages, or to physically delete these builds >> from the hydra database and re-evaluate the jobsets. Not sure what is >> best yet. >> >> Cheers, >> Rob >> >> On Tue, Jan 28, 2014 at 11:27 AM, Gergely Risko wrote: >>> Hi, >>> >>> Thanks, this looks great! >>> >>> But on the other hand now someone has to restart all the builds that >>> failed because of ghc being unavailable previously, e.g.: >>> http://hydra.nixos.org/job/nixpkgs/trunk/haskellPackages_ghc763.ghc.i686-linux >>> http://hydra.nixos.org/job/nixpkgs/trunk/haskellPackages.pipesParse.i686-linux >>> >>> But there are thousands more. :( >>> >>> Gergely >>> >>> On Tue, 28 Jan 2014 10:42:01 +0100, Rob Vermaas >>> writes: >>> The build should be available on hydra.nixos.org now. Cheers, Rob On Mon, Jan 27, 2014 at 9:12 PM, Peter Simons wrote: > Hi guys, > > I have a successful GHC 7.6.3 build for i686-linux available here: > > > http://hydra.cryp.to/job/nixpkgs/haskell-updates/haskellPackages.ghcPlain.i686-linux > > If hydra.nixos.org cannot compile that package for some reason, could > someone with appropriate admin privileges please import that closure > from my server into the /nix store on hydra.nix.org? I believe > > curl > "http://hydra.cryp.to/build/37672/nix/closure/ghc-7.6.3.closure.gz"; | > gunzip | nix-store --import > > should do the trick. > > Rob, maybe? > > Take care, > Peter > > ___ > 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 > > ___ > nix-dev mailing list > nix-dev@lists.science.uu.nl > http://lists.science.uu.nl/mailman/listinfo/nix-dev -- Rob Vermaas [email] rob.verm...@gmail.com ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] hydra admins: please take care of i686 GHC out of memory issues
Hi, Is it possible to make a change that only changes the libraries and other dependencies (e.g. git-annex)? Because by changing GHC itself we would trigger (most probably another failing) GHC rebuild. Gergely On Tue, 28 Jan 2014 12:02:16 +0100, Rob Vermaas writes: > Hi, > > that's a bit tricky, as the .drv's of the failed builds have been > garbage collected. We need to fix that in Hydra. For now, easiest > would be to add a change somewhere that'll trigger a rebuild of the > whole i686-linux ghc packages, or to physically delete these builds > from the hydra database and re-evaluate the jobsets. Not sure what is > best yet. > > Cheers, > Rob > > On Tue, Jan 28, 2014 at 11:27 AM, Gergely Risko wrote: >> Hi, >> >> Thanks, this looks great! >> >> But on the other hand now someone has to restart all the builds that >> failed because of ghc being unavailable previously, e.g.: >> http://hydra.nixos.org/job/nixpkgs/trunk/haskellPackages_ghc763.ghc.i686-linux >> http://hydra.nixos.org/job/nixpkgs/trunk/haskellPackages.pipesParse.i686-linux >> >> But there are thousands more. :( >> >> Gergely >> >> On Tue, 28 Jan 2014 10:42:01 +0100, Rob Vermaas >> writes: >> >>> The build should be available on hydra.nixos.org now. >>> >>> Cheers, >>> Rob >>> >>> On Mon, Jan 27, 2014 at 9:12 PM, Peter Simons wrote: Hi guys, I have a successful GHC 7.6.3 build for i686-linux available here: http://hydra.cryp.to/job/nixpkgs/haskell-updates/haskellPackages.ghcPlain.i686-linux If hydra.nixos.org cannot compile that package for some reason, could someone with appropriate admin privileges please import that closure from my server into the /nix store on hydra.nix.org? I believe curl "http://hydra.cryp.to/build/37672/nix/closure/ghc-7.6.3.closure.gz"; | gunzip | nix-store --import should do the trick. Rob, maybe? Take care, Peter ___ 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 ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] hydra admins: please take care of i686 GHC out of memory issues
Hi, that's a bit tricky, as the .drv's of the failed builds have been garbage collected. We need to fix that in Hydra. For now, easiest would be to add a change somewhere that'll trigger a rebuild of the whole i686-linux ghc packages, or to physically delete these builds from the hydra database and re-evaluate the jobsets. Not sure what is best yet. Cheers, Rob On Tue, Jan 28, 2014 at 11:27 AM, Gergely Risko wrote: > Hi, > > Thanks, this looks great! > > But on the other hand now someone has to restart all the builds that > failed because of ghc being unavailable previously, e.g.: > http://hydra.nixos.org/job/nixpkgs/trunk/haskellPackages_ghc763.ghc.i686-linux > http://hydra.nixos.org/job/nixpkgs/trunk/haskellPackages.pipesParse.i686-linux > > But there are thousands more. :( > > Gergely > > On Tue, 28 Jan 2014 10:42:01 +0100, Rob Vermaas > writes: > >> The build should be available on hydra.nixos.org now. >> >> Cheers, >> Rob >> >> On Mon, Jan 27, 2014 at 9:12 PM, Peter Simons wrote: >>> Hi guys, >>> >>> I have a successful GHC 7.6.3 build for i686-linux available here: >>> >>> >>> http://hydra.cryp.to/job/nixpkgs/haskell-updates/haskellPackages.ghcPlain.i686-linux >>> >>> If hydra.nixos.org cannot compile that package for some reason, could >>> someone with appropriate admin privileges please import that closure >>> from my server into the /nix store on hydra.nix.org? I believe >>> >>> curl "http://hydra.cryp.to/build/37672/nix/closure/ghc-7.6.3.closure.gz"; >>> | gunzip | nix-store --import >>> >>> should do the trick. >>> >>> Rob, maybe? >>> >>> Take care, >>> Peter >>> >>> ___ >>> 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 -- Rob Vermaas [email] rob.verm...@gmail.com ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] hydra admins: please take care of i686 GHC out of memory issues
Hi, Thanks, this looks great! But on the other hand now someone has to restart all the builds that failed because of ghc being unavailable previously, e.g.: http://hydra.nixos.org/job/nixpkgs/trunk/haskellPackages_ghc763.ghc.i686-linux http://hydra.nixos.org/job/nixpkgs/trunk/haskellPackages.pipesParse.i686-linux But there are thousands more. :( Gergely On Tue, 28 Jan 2014 10:42:01 +0100, Rob Vermaas writes: > The build should be available on hydra.nixos.org now. > > Cheers, > Rob > > On Mon, Jan 27, 2014 at 9:12 PM, Peter Simons wrote: >> Hi guys, >> >> I have a successful GHC 7.6.3 build for i686-linux available here: >> >> >> http://hydra.cryp.to/job/nixpkgs/haskell-updates/haskellPackages.ghcPlain.i686-linux >> >> If hydra.nixos.org cannot compile that package for some reason, could >> someone with appropriate admin privileges please import that closure >> from my server into the /nix store on hydra.nix.org? I believe >> >> curl "http://hydra.cryp.to/build/37672/nix/closure/ghc-7.6.3.closure.gz"; | >> gunzip | nix-store --import >> >> should do the trick. >> >> Rob, maybe? >> >> Take care, >> Peter >> >> ___ >> 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
Re: [Nix-dev] hydra admins: please take care of i686 GHC out of memory issues
The build should be available on hydra.nixos.org now. Cheers, Rob On Mon, Jan 27, 2014 at 9:12 PM, Peter Simons wrote: > Hi guys, > > I have a successful GHC 7.6.3 build for i686-linux available here: > > > http://hydra.cryp.to/job/nixpkgs/haskell-updates/haskellPackages.ghcPlain.i686-linux > > If hydra.nixos.org cannot compile that package for some reason, could > someone with appropriate admin privileges please import that closure > from my server into the /nix store on hydra.nix.org? I believe > > curl "http://hydra.cryp.to/build/37672/nix/closure/ghc-7.6.3.closure.gz"; | > gunzip | nix-store --import > > should do the trick. > > Rob, maybe? > > Take care, > Peter > > ___ > nix-dev mailing list > nix-dev@lists.science.uu.nl > http://lists.science.uu.nl/mailman/listinfo/nix-dev -- Rob Vermaas [email] rob.verm...@gmail.com ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] hydra admins: please take care of i686 GHC out of memory issues
Hi guys, I have a successful GHC 7.6.3 build for i686-linux available here: http://hydra.cryp.to/job/nixpkgs/haskell-updates/haskellPackages.ghcPlain.i686-linux If hydra.nixos.org cannot compile that package for some reason, could someone with appropriate admin privileges please import that closure from my server into the /nix store on hydra.nix.org? I believe curl "http://hydra.cryp.to/build/37672/nix/closure/ghc-7.6.3.closure.gz"; | gunzip | nix-store --import should do the trick. Rob, maybe? Take care, Peter ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] hydra admins: please take care of i686 GHC out of memory issues
On Fri, 10 Jan 2014 14:36:26 +0100, Rob Vermaas writes: > I have no idea what could be the problem, perhaps it is related to > some system setting, e.g. kernel. I've installed a 64-bit and a 32-bit virtual machine with nixos last week, just so that I can try building i686-linux ghc in both. My machines managed to reproduce exactly this hash (that fails on hydra): http://hydra.nixos.org/build/8427491 /nix/store/x1h3f7fg0ci9ybgs793v3x772k68jpbl-ghc-7.6.3 i686 5/5 times, amd64 7/7 times. Without any out of memory issues. So this must be some system setting issue on Hydra machines. How should we debug this? Can you please show my a "sysctl -a" output and a "ulimit -a" output in the same environment as being used by the GHC build on Hydra? Alternatively, is there some README/wiki/etc on setting up an exact replica of ike or kenny for testing? Or can you make an LVM snapshot of one of them and upload it somewhere (I can provide the space for it of course)? Not having an i686 GHC (and therefore git-annex, etc.) in binary cache is a really big issue for me :( So I'm happy to do what it takes to fix it. Gergely ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] hydra admins: please take care of i686 GHC out of memory issues
Hi. To me it's clear that some other job also depends on it (and got built first), so that's why it's "cached". On 01/22/2014 11:44 PM, Gergely Risko wrote: In the meantime can we please disable any parallelism during build for i686 (so no -j passing to any stage of the compiler) and try like that? Maybe we're just somehow hitting the 4G one process address space limit with threads or something. Parallel build already *was* disabled for GHC. Cf. rev. 28483364 for the default 7.6.3 and rev. cb2168 for most others. Also, would it too much of a waste of hydra resources to try 10 consecutive builds for_absolutely the same derivation_ and gather failure/success ratios? I think there was some discussion about auto-restarting builds with transient failures, but I don't remember what's the status/conclusions... Vlada 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 admins: please take care of i686 GHC out of memory issues
Hi, I'm just guessing here, but: - there are packages, that depend on GHC, e.g. git-annex: http://hydra.nixos.org/build/8421542 - this is the same evaluation, but the build number is smaller. So what I think is happening: - there is package X that build depends on GHC, - when package X is built, then GHC is built (and fails), - every next GHC try is cached failure (git-annex, ghc-wrapper, etc.). I don't know how to derive X via the hydra webinterface, but maybe it's easy for admins with SQL access, I really have no idea. And my guess is that once we find package X, that will contain the real (non-cached) build for GHC in this evaluation. If you check the hash of the GHC that is trying to be built, then you will see that it is actually changing between the success-failure transition, so this would really be a new one compared to the ones from 21st January. And about the failures: I've been thinking about this for the last 2-3 days and probably we're just being fooled by randomness. Before the stdenv merge, we thought that trunk is failing and stdenv is not, but actually if you review history, we have 3 different (with different hash, so not just cached) GHC build tries on trunk, all failed. But there are also failed ones on the stdenv trunk, circa 1/2 of the cases. So having 3 failes in a row is only p=1/8. Now that stdenv is merged, 2 builds are good and then the third one is broken. This can easily be all just random from a random source with 1/2 chance. I wanted to actually get some statistically significant evidence this by setting up my local build machine where I can build 10-20 times, but didn't get to it yet. Maybe with different settings: lot of parallelism (-j16), then with none (-j1), etc. In the meantime can we please disable any parallelism during build for i686 (so no -j passing to any stage of the compiler) and try like that? Maybe we're just somehow hitting the 4G one process address space limit with threads or something. Also, would it too much of a waste of hydra resources to try 10 consecutive builds for _absolutely the same derivation_ and gather failure/success ratios? Thanks, Gergely On Wed, 22 Jan 2014 13:59:17 +0100, Peter Simons writes: > Hi guys, > > I am confused. According to [1] we've had a working GHC build for Linux/i686 > in evaluations 8394199 and 8396207 -- immediately after the stdenv-updates > merge. Then Hydra ran a third build, [2], and that ended up being a "cached > failure". Yet, there were no failed builds since the stdenv merger! How is > that possible? > > Am I missing something? > > Take care, > Peter > > [1] http://hydra.nixos.org/job/nixpkgs/trunk/haskellPackages.ghc.i686-linux > [2] http://hydra.nixos.org/build/8427824 ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] hydra admins: please take care of i686 GHC out of memory issues
Hi guys, I am confused. According to [1] we've had a working GHC build for Linux/i686 in evaluations 8394199 and 8396207 -- immediately after the stdenv-updates merge. Then Hydra ran a third build, [2], and that ended up being a "cached failure". Yet, there were no failed builds since the stdenv merger! How is that possible? Am I missing something? Take care, Peter [1] http://hydra.nixos.org/job/nixpkgs/trunk/haskellPackages.ghc.i686-linux [2] http://hydra.nixos.org/build/8427824 ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] hydra admins: please take care of i686 GHC out of memory issues
Hi, > > The memory problems seems to be reproducible and seems nothing to do > > with a lack of memory (it was running on a server with enough memory > > available, 80GB). > > I don't know why the build fails on that particular build machine, but I > am pretty sure that it's not a problem with the GHC build per se, because > it succeeds just fine when I try it: > > > http://hydra.cryp.to/job/nixpkgs/haskell-updates/haskellPackages.ghcPlain.i686-linux > > So whatever it is that's causing this error, I tend to believe that it *is* > related to the machine in some way. Restarted the build, and made sure it was building on a different system (was ike before, now kenny) and the error was the same (except for the number of bytes it failed to request.) [1]. I have no idea what could be the problem, perhaps it is related to some system setting, e.g. kernel. Cheers, Rob [1] http://hydra.nixos.org/build/7635977 -- Rob Vermaas [email] rob.verm...@gmail.com ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] hydra admins: please take care of i686 GHC out of memory issues
On 01/09/2014 04:06 PM, Gergely Risko wrote: > http://hydra.cryp.to/job/nixpkgs/haskell-updates/haskellPackages.ghcPlain.i686-linux Do you happen to have publicly available binary cache exported for these builds? After running sudo nix-pull http://hydra.cryp.to/jobset/nixpkgs/haskell-updates/channel/latest/MANIFEST you should have these binaries used by nix tools. Vlada 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 admins: please take care of i686 GHC out of memory issues
On Thu, 09 Jan 2014 11:16:05 +0100, Peter Simons writes: > > http://hydra.cryp.to/job/nixpkgs/haskell-updates/haskellPackages.ghcPlain.i686-linux Do you happen to have publicly available binary cache exported for these builds? Gergely ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] hydra admins: please take care of i686 GHC out of memory issues
On Thu, 09 Jan 2014 11:22:41 +0100, Vladimír Čunát writes: > On 01/09/2014 11:16 AM, Peter Simons wrote: >> So whatever it is that's causing this error, I tend to believe that it*is* >> related to the machine in some way. > > Note that the jobs built on stdenv-updates fine a few days ago, and I > think there are no specific haskell-related changes there. Can it be that the build machine somehow used too many threads? This is just a hunch, but can we maybe test the build with -j1? Maybe with many CPUs it uses much more RAM or one process tries to use more than 4G ram which is not OK on i686. Any other tips what should I try locally to reproduce this issue? Also, the error is consistently happening, but always at a different point in the build process, so it is really strange. On the other hand, the end result (haskell missing from bincache) is really annoying :( Gergely ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] hydra admins: please take care of i686 GHC out of memory issues
On 01/09/2014 11:16 AM, Peter Simons wrote: So whatever it is that's causing this error, I tend to believe that it*is* related to the machine in some way. Note that the jobs built on stdenv-updates fine a few days ago, and I think there are no specific haskell-related changes there. Vlada 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 admins: please take care of i686 GHC out of memory issues
Hi Rob, > The memory problems seems to be reproducible and seems nothing to do > with a lack of memory (it was running on a server with enough memory > available, 80GB). I don't know why the build fails on that particular build machine, but I am pretty sure that it's not a problem with the GHC build per se, because it succeeds just fine when I try it: http://hydra.cryp.to/job/nixpkgs/haskell-updates/haskellPackages.ghcPlain.i686-linux So whatever it is that's causing this error, I tend to believe that it *is* related to the machine in some way. Take care, Peter ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] hydra admins: please take care of i686 GHC out of memory issues
Hi, The memory problems seems to be reproducible and seems nothing to do with a lack of memory (it was running on a server with enough memory available, 80GB). Cheers, Rob On Wed, Jan 8, 2014 at 4:56 PM, Gergely Risko wrote: > Hi, > > Can someone please take a look at this and maybe add more swap space or > something? > > http://hydra.nixos.org/job/nixpkgs/trunk/haskellPackages.ghc.i686-linux > > I think this build is broken since the hydra cluster has been moved, but > this might be unrelated. > > This causes all of haskell not being updated in the binary cache for > i686, which makes installation slw. :) > > If there are human resource issues here, I'm happy to do 1-2 hours/week > hydra administration and handling of tickets like this. > > Thanks, > Gergely > > ___ > nix-dev mailing list > nix-dev@lists.science.uu.nl > http://lists.science.uu.nl/mailman/listinfo/nix-dev -- Rob Vermaas [email] rob.verm...@gmail.com ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
