[Nix-dev] how to debug the binary cache

[Vladimír Čunát]

Hi.

On 09/11/2013 06:41 PM, Gergely Risko wrote:
> Here is a build: http://hydra.nixos.org/build/6046495
>
> And here is the corresponding narinfo:
> HEAD http://cache.nixos.org/rij57njvzwsbc2iwdscgnk47l8zrm62n.narinfo
>
> But actually the .narinfo doesn't exist yet and I'd like to know why and
> how long do I have to wait before the binary cache gets updated after a
> hydra build.  Do every build go to the binary cache?  How is that
> decided?  Is there a dashboard somewhere to check?  How about old stuff,
> what is the garbage collection policy on the binary cache?

I only know little (and I can't directly find out or affect it). AFAIK:

- Binary cache is created only from the master branches (speaking of 
nixpkgs and nixos).
- Channel is only updated after the "unstable" job builds successfully 
(depends on some jobs deemed essential). Maybe that's the only time when 
the binary cache is also updated.
- It's currently hosted in Amazon cloud and paid for LogicBlox (Eelco's 
employer).
- The build farm itself seems to behave very strange during the last 
week or so (does few builds, maybe some other things are broken right now).

> Any pointers?

As soon as any job finishes, you can get the package through the 
one-click installs or channels for the job/jobset. However, we're asked 
to use that sparingly, as the results are generated on-demand and put 
more stress on the Hydra front-end server. (I think there is no other 
option if e.g. one wants to try x-updates or stdenv-updates.)


Vlada


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3251 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.science.uu.nl/pipermail/nix-dev/attachments/20130912/49c706d0/attachment.bin