This mailing list is for discussing the development of Guix.
This discussion about filtering in mail clients and associated insults
and expressions of frustration are not on topic.
Please let it go.
--
Ricardo
On 07/01/2017 at 14:01 Leo Famulari writes:
> On Sat, Jul 01, 2017 at 05:36:04PM +, ng0 wrote:
[...]
>> 0: What is it these days? Is hydra now just a in-retirement frontend
>> for cuirass or how does bayfront work these days? I understand cuirass,
>> not hydra.
>
> ... Bayfront is still not fu
On Sat, Jul 01, 2017 at 07:24:25PM +, ng0 wrote:
> > First, is there some outstanding bug that needs to be fixed? It's
> > frustrating to get messages like this without any context.
>
> Yes, but I certainly will not run reconfigure on here from HEAD
> again. When I ran into this I had not git
Leo Famulari transcribed 3.2K bytes:
> On Sat, Jul 01, 2017 at 05:36:04PM +, ng0 wrote:
> > (This is brief and incomplete, just the way I see it right now)
>
> [...]
>
> > imagine that _before_ commits end up in master we build a set of
> > virtual systems which at least must:
> >
> > - be b
On Sat, Jul 01, 2017 at 05:36:04PM +, ng0 wrote:
> (This is brief and incomplete, just the way I see it right now)
[...]
> imagine that _before_ commits end up in master we build a set of
> virtual systems which at least must:
>
> - be build successfully
> - run through the initrd
> - briefl
deployment? at least I mean the
commit getting into the master branch) isn't really acceptable
from a technical and social perspective.
I have no formal solution but I want to have this dicussion
because I can no longer stand the state of how often "assumed
to work" commits are pushed. Q
(This is the continuation of a thread about the memory requirements of
job evaluation on Hydra.)
Here’s a run in conditions similar to those of Hydra:
--8<---cut here---start->8---
$ \time -v guile -l build-aux/hydra/gnu-system.scm -c '(use-modules (guix))
(wi
