GNU bug report logs - #28484
Some steps and questions for Cuirass

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 28484 in the body.
You can then email your comments to 28484 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Jan Nieuwenhuizen <janneke <at> gnu.org>
To: guix-patches <at> gnu.org
Subject: Some steps and questions for Cuirass
Date: Sun, 17 Sep 2017 22:11:53 +0200

When Cuirass creates a new working directory from a guix.git clone, it tries
to build guix but fails like this

    /gnu/store/jqs80jq4j9z06p2vb9f7djv9k7jmc3d4-profile/bin/msgmerge: cannot create output file "de.po": Permission denied
    make[3]: *** [Makefile:255: de.po] Error 1
    make[3]: *** Waiting for unfinished jobs....

...although that may be a feature?

Patch 1/3 fixes this build problem...however now Cuirass rebuilds *all* of
guix (.go files) for each update of guix.git that it tracks.  When playing
with Cuirass to set it up, it's handy to only build `hello'.  Rebuilding all
of guix for each commit even if it fast-forwards, do we need/want that?

Patch 2/3 allows to test with other packages than "hello" or everything by
using a spec like

     ((#:name . "guix")
      (#:url . "git://git.savannah.gnu.org/guix.git")
      (#:load-path . ".")
      (#:file . "examples/gnu-system.scm")
      (#:proc . hydra-jobs)
      (#:arguments (subset . ("hello" "grep")))
      (#:branch . "master"))

Because this build recipe and thus this feature belongs in the repository
we're building, I also added a patch (the last one) for Guix itself that
implements this.

Patch 3/3 is the one I'm least happy with.  When building many more packages
than only `hello', Cuirass will not give any feedback until after everything
is built.  The Emacs interface under M-x guix-hydra-latests-builds is very
nice, but polling for that less so.

As the comment in the file already says

    ;; Register the results in the database.
    ;; XXX: The 'build-derivations' call is blocking so we end updating the
    ;; database potentially long after things have been built.

we probably want feedback (or guix-hydra-latests-builds availability) per
package...but any ideas how to do that?  We'd have to wrap/closure that into
building the derivations?

Greetings,
janneke

Message #8 received at 28484 <at> debbugs.gnu.org (full text, mbox):

From: Mathieu Othacehe <m.othacehe <at> gmail.com>
To: Jan Nieuwenhuizen <janneke <at> gnu.org>
Cc: 28484 <at> debbugs.gnu.org
Subject: Re: [bug#28484] Some steps and questions for Cuirass
Date: Mon, 18 Sep 2017 13:51:58 +0200

Hi Jan,

> ...although that may be a feature?

I don't think so, patch 1 & 2 LGTM.

> Patch 3/3 is the one I'm least happy with.  When building many more packages
> than only `hello', Cuirass will not give any feedback until after everything
> is built.  The Emacs interface under M-x guix-hydra-latests-builds is very
> nice, but polling for that less so.
>
> As the comment in the file already says
>
>     ;; Register the results in the database.
>     ;; XXX: The 'build-derivations' call is blocking so we end updating the
>     ;; database potentially long after things have been built.
>
> we probably want feedback (or guix-hydra-latests-builds availability) per
> package...but any ideas how to do that?  We'd have to wrap/closure that into
> building the derivations?

Now that Cuirass supports M-x guix-hydra-latests-builds, the next step
is to detect build start/stop (maybe via guix build log parsing see:
https://lists.gnu.org/archive/html/guix-devel/2017-07/msg00221.html).

This way, for each new commit in guix, cuirass will only insert in
database the derivation that were built. Plus, it will be possible to
insert the build in db when it starts and update its status when it
stops/fails.

Until this is developed, patch 3 LGTM too !

Mathieu

Message #13 received at 28484-done <at> debbugs.gnu.org (full text, mbox):

From: Jan Nieuwenhuizen <janneke <at> gnu.org>
To: Mathieu Othacehe <m.othacehe <at> gmail.com>
Cc: 28484-done <at> debbugs.gnu.org
Subject: Re: [bug#28484] Some steps and questions for Cuirass
Date: Mon, 18 Sep 2017 17:44:08 +0200

Mathieu Othacehe writes:

> I don't think so, patch 1 & 2 LGTM.

Thanks!

> Now that Cuirass supports M-x guix-hydra-latests-builds, the next step
> is to detect build start/stop (maybe via guix build log parsing see:
> https://lists.gnu.org/archive/html/guix-devel/2017-07/msg00221.html).
>
> This way, for each new commit in guix, cuirass will only insert in
> database the derivation that were built. Plus, it will be possible to
> insert the build in db when it starts and update its status when it
> stops/fails.

Ah that makes sense.  Thanks for sharing this thread.

> Until this is developed, patch 3 LGTM too !

Thanks, pushed to guix-cuirass master as 87ad259dba7de38b6e3ab954cd7b2f655358d877

janneke

-- 
Jan Nieuwenhuizen <janneke <at> gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.