unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: 27654@debbugs.gnu.org
Subject: [bug#27654] [PATCH] base: Report evaluation error.
Date: Wed, 12 Jul 2017 22:54:05 +0200	[thread overview]
Message-ID: <87vamxbclu.fsf@gnu.org> (raw)
In-Reply-To: <868tjtmx96.fsf@gmail.com> (Mathieu Othacehe's message of "Wed, 12 Jul 2017 18:32:37 +0200")

[-- Attachment #1: Type: text/plain, Size: 650 bytes --]

Mathieu Othacehe <m.othacehe@gmail.com> skribis:

> From c9a3325c1c021564edc689ff2421b04c9e794052 Mon Sep 17 00:00:00 2001
> From: Mathieu Othacehe <m.othacehe@gmail.com>
> Date: Tue, 11 Jul 2017 19:15:08 +0200
> Subject: [PATCH] base: Report evaluation error.
>
> * src/cuirass/base.scm (evaluate): Report an error if eof-object? is true on
>   data read from port. Otherwise, suppose that data are correct and keep thins
>   going.

Please mention the new ‘&evaluation-error’ in here.

BTW, shouldn’t ‘process-specs’ protect against it, so that Cuirass
doesn’t stop as soon as it encounters an evaluation error?  Like:


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 788 bytes --]

diff --git a/src/cuirass/base.scm b/src/cuirass/base.scm
index fc3cc1a..3d19bda 100644
--- a/src/cuirass/base.scm
+++ b/src/cuirass/base.scm
@@ -185,9 +185,12 @@ if required.  Return the last commit ID on success, #f otherwise."
                                #:use-substitutes? (%use-substitutes?)
                                #:keep-going? #t)
 
+            (guard (c ((evaluation-error? c)
+                       ;; Report the problem in the log...
+                       #f))
               (let* ((spec* (acons #:current-commit commit spec))
                      (jobs  (evaluate store db spec*)))
-              (build-packages store db jobs))))
+                (build-packages store db jobs)))))
         (db-add-stamp db spec commit))))
 
   (for-each process jobspecs))

[-- Attachment #3: Type: text/plain, Size: 60 bytes --]


OK with something along these lines, thanks!

Ludo’.

  reply	other threads:[~2017-07-12 20:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-11 17:16 [bug#27654] [PATCH] base: Report evaluation error Mathieu Othacehe
2017-07-12 12:15 ` Ludovic Courtès
2017-07-12 16:32   ` Mathieu Othacehe
2017-07-12 20:54     ` Ludovic Courtès [this message]
2017-07-30 10:47       ` bug#27654: " Mathieu Othacehe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vamxbclu.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=27654@debbugs.gnu.org \
    --cc=m.othacehe@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).