From: builder@sourceware.org
To: elfutils-devel@sourceware.org
Subject: ☠ Buildbot (Sourceware): elfutils - failed compile (failure) (main)
Date: Tue, 14 Nov 2023 17:37:40 +0000 [thread overview]
Message-ID: <20231114173740.F3C943858D28@sourceware.org> (raw)
A new failure has been detected on builder elfutils-debian-armhf while building elfutils.
Full details are available at:
https://builder.sourceware.org/buildbot/#builders/6/builds/239
Build state: failed compile (failure)
Revision: f1a381fb050650a9c15e15d0102967df3f0a6a03
Worker: debian-armhf
Build Reason: (unknown)
Blamelist: Paul Pluzhnikov <ppluzhnikov@google.com>
Steps:
- 0: worker_preparation ( success )
- 1: set package name ( success )
- 2: git checkout ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/6/builds/239/steps/2/logs/stdio
- 3: autoreconf ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/6/builds/239/steps/3/logs/stdio
- 4: configure ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/6/builds/239/steps/4/logs/stdio
- config.log: https://builder.sourceware.org/buildbot/#builders/6/builds/239/steps/4/logs/config_log
- 5: get version ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/6/builds/239/steps/5/logs/stdio
- property changes: https://builder.sourceware.org/buildbot/#builders/6/builds/239/steps/5/logs/property_changes
- 6: make ( failure )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/6/builds/239/steps/6/logs/stdio
A new failure has been detected on builder elfutils-debian-i386 while building elfutils.
Full details are available at:
https://builder.sourceware.org/buildbot/#builders/17/builds/250
Build state: failed compile (failure)
Revision: f1a381fb050650a9c15e15d0102967df3f0a6a03
Worker: debian-i386
Build Reason: (unknown)
Blamelist: Paul Pluzhnikov <ppluzhnikov@google.com>
Steps:
- 0: worker_preparation ( success )
- 1: set package name ( success )
- 2: git checkout ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/17/builds/250/steps/2/logs/stdio
- 3: autoreconf ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/17/builds/250/steps/3/logs/stdio
- 4: configure ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/17/builds/250/steps/4/logs/stdio
- config.log: https://builder.sourceware.org/buildbot/#builders/17/builds/250/steps/4/logs/config_log
- 5: get version ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/17/builds/250/steps/5/logs/stdio
- property changes: https://builder.sourceware.org/buildbot/#builders/17/builds/250/steps/5/logs/property_changes
- 6: make ( failure )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/17/builds/250/steps/6/logs/stdio
next reply other threads:[~2023-11-14 17:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 17:37 builder [this message]
2024-03-01 20:25 builder
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=20231114173740.F3C943858D28@sourceware.org \
--to=builder@sourceware.org \
--cc=elfutils-devel@sourceware.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.
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).