unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
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 16:35:42 +0200	[thread overview]
Message-ID: <87v9fo7nb5.fsf@yamatai> (raw)
In-Reply-To: <87y2kk7rni.fsf@yamatai>

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


Guillaume Le Vaillant <glv@posteo.net> skribis:

> 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:
>>> [...]
>>>
>>> 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?

Ok, I started a local Cuirass, I reproduced the evaluation failure, and
I think I found the problem: Cuirass was choking on the definition of
the ecl-slynk package. I fixed it and know the evaluation has
been 'In progress...' for 15 minutes.
Then, if the evaluation completes successfully, and if there are no
objections, I'll push the updated staging branch.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2020-10-05 14:36 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   ` Failing CI evaluation for staging branch Guillaume Le Vaillant
2020-10-05 14:35     ` Guillaume Le Vaillant [this message]
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=87v9fo7nb5.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).