GNU bug report logs -
#28484
Some steps and questions for Cuirass
Previous Next
Reported by: Jan Nieuwenhuizen <janneke <at> gnu.org>
Date: Sun, 17 Sep 2017 20:14:02 UTC
Severity: normal
Done: Jan Nieuwenhuizen <janneke <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your bug report
#28484: Some steps and questions for Cuirass
which was filed against the guix-patches package, has been closed.
The explanation is attached below, along with your original report.
If you require more details, please reply to 28484 <at> debbugs.gnu.org.
--
28484: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=28484
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
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
[Message part 3 (message/rfc822, inline)]
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
This bug report was last modified 7 years and 248 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.