From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: 67610@debbugs.gnu.org
Subject: bug#67610: Build guile-hoot.powerpc64le-linux on master is broken.
Date: Sun, 03 Dec 2023 18:39:30 -0500 [thread overview]
Message-ID: <875y1eyhxp.fsf@gmail.com> (raw)
In-Reply-To: <CAJ=RwfZyEdMktVUfRkdyTC1-O9o2PGxh8RYdyOvYr_oLgQDmVw@mail.gmail.com> (David Thompson's message of "Sun, 3 Dec 2023 15:11:20 -0500")
Hi David,
"Thompson, David" <dthompson2@worcester.edu> writes:
> On Sun, Dec 3, 2023 at 1:35 PM Maxim Cournoyer
> <maxim.cournoyer@gmail.com> wrote:
>>
>> Hello,
>>
>> cuirass@gnu.org (Cuirass) writes:
>>
>> > <p>The build <b>guile-hoot.powerpc64le-linux</b> for specification <b>master</b> is
>> > broken. You can find the detailed information about this build <a
>> > href="https://ci.guix.gnu.org/build/2735982/details">here</a>.</p>
>> >
>> > https://ci.guix.gnu.org/build/2735982/details
>>
>> The latest guile-hoot newly fails on powerpc64le:
[...]
> Hmm I'd need the contents of the failing test logs to have an idea
> about what's happening. All I can tell from what's there is that any
> test file that invokes the compiler fails. I don't have any powerpc
> hardware so I can't reproduce myself.
Nevermind, it appears the above failure was correctly in a subsequent
commit; I should have checked if this CI failure had been later resolved
before sending this message :-).
--
Thanks,
Maxim
prev parent reply other threads:[~2023-12-03 23:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2220@guix-ci.nnrss>
2023-12-03 18:34 ` bug#67610: Build guile-hoot.powerpc64le-linux on master is broken Maxim Cournoyer
[not found] ` <handler.67610.B.170162851512536.ack@debbugs.gnu.org>
2023-12-03 18:38 ` bug#67610: Acknowledgement (Build guile-hoot.powerpc64le-linux on master is broken.) Maxim Cournoyer
2023-12-03 20:11 ` bug#67610: Build guile-hoot.powerpc64le-linux on master is broken Thompson, David
2023-12-03 23:39 ` Maxim Cournoyer [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875y1eyhxp.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=67610@debbugs.gnu.org \
--cc=dthompson2@worcester.edu \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.