From: Guillaume Le Vaillant <glv@posteo.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Failing CI evaluation for staging branch
Date: Mon, 05 Oct 2020 15:01:53 +0200 [thread overview]
Message-ID: <87y2kk7rni.fsf@yamatai> (raw)
In-Reply-To: <877ds42760.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2583 bytes --]
Ludovic Courtès <ludo@gnu.org> skribis:
> Hi Guillaume,
>
> Guillaume Le Vaillant <glv@posteo.net> skribis:
>
>> Currently no substitutes are built for the testing branch because the
>> evaluation fails. The log at https://ci.guix.gnu.org/eval/16794/log/raw
>> ends with:
>
> You mean the ‘staging’ branch?
>
Yes, I meant 'staging'. I often type 'testing' instead of 'staging',
probably that pesky muscle memory!.
>> guix/inferior.scm:247:2: ERROR:
>> 1. &inferior-exception:
>> arguments: (keyword-argument-error #f "Unrecognized keyword" () (#:builder))
>> inferior: #<<inferior> pid: pipe socket: #<input-output: string 7f07952ae690> close: #<procedure close-pipe (p)> version: (0 1 1) packages: #<promise #<procedure 7f07951d62c0 at guix/inferior.scm:162:32 ()>> table: #<promise #<procedure 7f079e960480 at guix/inferior.scm:163:32 ()>>>
>> stack: ((#f ("ice-9/boot-9.scm" 1763 13)) (raise-exception ("ice-9/boot-9.scm" 1666 16)) (raise-exception ("ice-9/boot-9.scm" 1668 16)) (#f ("guix/build-system/asdf.scm" 279 2)) (thunk ("guix/packages.scm" 1397 22)) (package-derivation ("guix/packages.scm" 1079 16)) (job ("gnu/ci.scm" 383 24)) (filter-map ("srfi/srfi-1.scm" 690 23)) (#f ("gnu/ci.scm" 497 31)) (map1 ("srfi/srfi-1.scm" 585 17)) (append-map ("srfi/srfi-1.scm" 672 15)) (hydra-jobs ("gnu/ci.scm" 482 4)) (#f ("ice-9/eval.scm" 158 9)) (#f ("ice-9/eval.scm" 158 9)) (with-exception-handler ("ice-9/boot-9.scm" 1735 10)) (call-with-prompt ("ice-9/boot-9.scm" 717 2)) (dynamic-wind ("ice-9/boot-9.scm" 141 2)) (#f (#f #f #f)) (#f ("guix/repl.scm" 92 21)) (with-exception-handler ("ice-9/boot-9.scm" 1735 10)) (with-exception-handler ("ice-9/boot-9.scm" 1730 15)) (#f ("guix/repl.scm" 119 7)))
>>
>> If I understand this correctly, there's a '#:builder' keyword somewhere
>> that is causing a problem. Does someone know where it can come from, or
>> how to fix the issue?
>
> Right. I’d look at guix/build-system/asdf.scm:279:2 on that branch (per
> the inferior stack trace above). Does that give useful info?
I didn't see any obvious problem in that file; the strange thing is that
'make', 'make as-derivation' and './pre-inst-env guix build ...' all
work fine.
In a local branch I merged the current master (3699ed6) into staging
(de96ed1) and I'm going to try to start a local cuirass daemon to see
wether I can reproduce the issue or not.
Given that merging master in staging hasn't been done in a while, should
I also push my updated staging branch, or maybe someone is already
working on it?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2020-10-05 13:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 9:41 Failing CI evaluation for testing branch Guillaume Le Vaillant
2020-10-05 12:23 ` Ludovic Courtès
2020-10-05 13:01 ` Guillaume Le Vaillant [this message]
2020-10-05 14:35 ` Failing CI evaluation for staging branch Guillaume Le Vaillant
2020-10-05 17:10 ` Guillaume Le Vaillant
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=87y2kk7rni.fsf@yamatai \
--to=glv@posteo.net \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/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).