From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: andremegafone@gmail.com, GNU Debbugs <control@debbugs.gnu.org>,
67042@debbugs.gnu.org
Subject: bug#67042: ecl-cl-pcg fails to build due to a flaky test (was: Re: bug#67042: ecl-seedable-rng recently broken)
Date: Sun, 03 Dec 2023 19:26:04 -0500 [thread overview]
Message-ID: <87edg2vmn7.fsf_-_@gmail.com> (raw)
In-Reply-To: <8734xd79sg.fsf@kitej> (Guillaume Le Vaillant's message of "Fri, 10 Nov 2023 18:01:12 +0000")
retitle 67042 ecl-cl-pcg fails to build due to a flaky test
quit
Hi Guillaume,
Guillaume Le Vaillant <glv@posteo.net> writes:
> Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
>
>> Hi,
>>
>> guix-commits@gnu.org writes:
>>
>>> glv pushed a commit to branch master
>>> in repository guix.
>>>
>>> commit 42bec70a91d2205371c96287bcf565dcc5f5dd74
>>> Author: Andre A. Gomes <andremegafone@gmail.com>
>>> AuthorDate: Thu Nov 2 11:19:41 2023 +0200
>>>
>>> gnu: cl-slynk: Update to 1.0.43-9.9c43bf6.
>>>
>>> * gnu/packages/lisp-xyz.scm (sbcl-slynk): Update to 1.0.43-9.9c43bf6.
>>>
>>> Signed-off-by: Guillaume Le Vaillant <glv@posteo.net>
>>> Change-Id: I84ff141b7eefff470f72493d02f2cc24f02db7cf
>>
>> This commit or some preceding cl-* ones broke ecl-seedable-rng,
>> according to notifications from the CI:
>>
>> ecl-seedable-rng.x86_64-linux on master is broken
>>
>> Potentially related failures:
>>
>> - sbcl-cl-freetype2 (https://ci.guix.gnu.org/build/2584694/details)
>> - ecl-origin (https://ci.guix.gnu.org/build/2580823/details)
>>
>> See: https://ci.guix.gnu.org/build/2585168/details
>
> Hi.
>
> Locally I can build sbcl-cl-freetype2 and ecl-origin without issue.
>
> Concerning ecl-seedable-rng, there's something funny going on. The build
> details on the CI list only 1 dependency (ecl-ironclad), but there
> should be 3; ecl-cl-pcg and ecl-golden-utils are missing. And it is in
> fact the ecl-cl-pcg dependency that fails to build (because of a test).
> However, neither ecl-cl-pcg nor its dependencies have been updated
> recently, so why did the CI need to rebuild it, and why did it start
> failing?
Tests can sometimes be flaky (fail non-deterministically). The best
course of action in these situations is to 1. report the problem
upstream and 2. disable the test in our packaging. Re-titling
accordingly.
Cuirass mixing up derivations is tracked in bug #65505.
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-12-04 0:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <169954040581.31035.1536863063117085164@vcs2.savannah.gnu.org>
[not found] ` <20231109143335.B7FC1C0C199@vcs2.savannah.gnu.org>
2023-11-10 14:04 ` bug#67042: ecl-seedable-rng recently broken Maxim Cournoyer
2023-11-10 18:01 ` Guillaume Le Vaillant
2023-12-04 0:26 ` Maxim Cournoyer [this message]
2023-12-05 9:26 ` bug#67042: ecl-cl-pcg fails to build due to a flaky test (was: Re: bug#67042: ecl-seedable-rng recently broken) 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=87edg2vmn7.fsf_-_@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=67042@debbugs.gnu.org \
--cc=andremegafone@gmail.com \
--cc=control@debbugs.gnu.org \
--cc=glv@posteo.net \
/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).