Re: Cuirass news

[Ricardo Wurmus]

Hi Ludo,

> Over the last few days, out of frustration ;-), I hacked Cuirass to
> improve several things:

Oh yeah!  That’s great.

>   • Logging is improved: useful events are logged, including build
>     started/succeeded/failed (using a variant of what I proposed in the
>     Guix ‘wip-ui’ branch).  This makes it much easier to understand
>     what’s going on!

Finally!  Better logging alone would be a reason to celebrate :)

IIRC the wip-ui branch parsed the address@hidden messages of the daemon.
I didn’t find this in your commits to Cuirass, though.

>   • Restarting unfinished builds: it’s common, especially when testing,
>     to interrupt Cuirass, leaving a number of builds unfinished or not
>     even started.  Now Cuirass restarts those upon startup.

Also very useful.  Does this mean Cuirass resumes work more quickly now
whereas previously it would have to compute the full evaluation after a
restart?

I wonder about commit 49a341866afabe64c8ac3b8d93c64d2b6b20895d: you’re
chunking the number of derivations because guix-daemon doesn’t perform
well when it is asked to build lots of derivations at once.  Is it
possible to parse, lock, and run individual derivations in the daemon
when presented with lots of them, or is there a good reason why each of
these phases is executed for all derivations?

> And!  This brings a whole set of new bugs that I’m hunting notably on
> berlin (which may thus lag behind…).

I see that there are a bunch of spawn-fiber invocations with
“with-database” bodies.  Maybe I remember this wrong, but I thought
sqlite doesn’t support concurrent database access.

> Overall I think it’ll make Cuirass
> easier to work with and more “introspectable”.

I think so too.  Thanks again.

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net