From: "Frank Ch. Eigler" <fche@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: "Martin Liška" <mliska@suse.cz>, elfutils-devel@sourceware.org
Subject: Re: ☠ Buildbot (GNU Toolchain): elfutils-try-debian-armhf - failed compile (failure) (users/marxin/try-zstd-support-v2)
Date: Wed, 21 Dec 2022 09:54:21 -0500 [thread overview]
Message-ID: <20221221145421.GA28571@redhat.com> (raw)
In-Reply-To: <20e14ca61f27119efca8e1e38292d82ac3048ec8.camel@klomp.org>
Hi -
> [...]
> Unfortunately buildbot itself doesn't show the config.log.
> Trying to get that...
Ah darn. It would have been saved in bunsen, but the buildbot
configuration means that a make-stage failure means it won't even try.
- FChE
next prev parent reply other threads:[~2022-12-21 14:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221221111547.74C4C385B50B@sourceware.org>
2022-12-21 14:20 ` Martin Liška
2022-12-21 14:42 ` Mark Wielaard
2022-12-21 14:54 ` Frank Ch. Eigler [this message]
2022-12-21 15:21 ` Mark Wielaard
2022-12-21 18:29 ` Martin Liška
2022-12-21 23:38 ` Mark Wielaard
2022-12-22 9:09 ` Martin Liška
2022-12-22 18:17 ` Mark Wielaard
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=20221221145421.GA28571@redhat.com \
--to=fche@redhat.com \
--cc=elfutils-devel@sourceware.org \
--cc=mark@klomp.org \
--cc=mliska@suse.cz \
/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.
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).