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-updat
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
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
>
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
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
