From: builder@sourceware.org
To: "Aleksei Vetrov" <vvvvvv@google.com>,
"Ben Woodard" <woodard@redhat.com>,
"Ben Woodard via Libabigail" <libabigail@sourceware.org>,
"Dodji Seketeli" <dodji@redhat.com>,
"Dodji Seketeli" <dodji@seketeli.org>,
"Frederic Cambus" <fred@statdns.com>,
"Giuliano Procida" <gprocida@google.com>,
"Guillermo E. Martinez" <guillermo.e.martinez@oracle.com>,
"Guillermo E. Martinez via Libabigail"
<libabigail@sourceware.org>, "Mark Wielaard" <mark@klomp.org>,
"Matthias Maennich" <maennich@google.com>,
"Petr Pavlu" <petr.pavlu@suse.com>, "Sam James" <sam@gentoo.org>,
"Vanessa Sochat" <sochat1@llnl.gov>,
"Xiaole He" <hexiaole@kylinos.cn>,
"Xiaole He via Libabigail" <libabigail@sourceware.org>,
vsoch <vsoch@users.noreply.github.com>
Subject: ☠ Buildbot (Sourceware): libabigail - failed test (failure) (master)
Date: Thu, 02 Mar 2023 21:57:59 +0000 [thread overview]
Message-ID: <20230302215759.9DDC73858C83@sourceware.org> (raw)
A failed build has been detected on builder libabigail-gentoo-sparc while building libabigail.
Full details are available at:
https://builder.sourceware.org/buildbot/#builders/234/builds/22
Build state: failed test (failure)
Revision: 0c1936eecc777d2c5717f88430365b9dcc989f7a
Worker: gentoo-sparc-big
Build Reason: (unknown)
Blamelist: Aleksei Vetrov <vvvvvv@google.com>, Ben Woodard <woodard@redhat.com>, Ben Woodard via Libabigail <libabigail@sourceware.org>, Dodji Seketeli <dodji@redhat.com>, Dodji Seketeli <dodji@seketeli.org>, Frederic Cambus <fred@statdns.com>, Giuliano Procida <gprocida@google.com>, Guillermo E. Martinez <guillermo.e.martinez@oracle.com>, Guillermo E. Martinez via Libabigail <libabigail@sourceware.org>, Mark Wielaard <mark@klomp.org>, Matthias Maennich <maennich@google.com>, Petr Pavlu <petr.pavlu@suse.com>, Sam James <sam@gentoo.org>, Vanessa Sochat <sochat1@llnl.gov>, Xiaole He <hexiaole@kylinos.cn>, Xiaole He via Libabigail <libabigail@sourceware.org>, vsoch <vsoch@users.noreply.github.com>
Steps:
- 0: worker_preparation ( success )
- 1: git checkout ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/234/builds/22/steps/1/logs/stdio
- 2: autoreconf ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/234/builds/22/steps/2/logs/stdio
- 3: configure ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/234/builds/22/steps/3/logs/stdio
- config.log: https://builder.sourceware.org/buildbot/#builders/234/builds/22/steps/3/logs/config_log
- 4: make ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/234/builds/22/steps/4/logs/stdio
- 5: make check ( failure )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/234/builds/22/steps/5/logs/stdio
- test-suite.log: https://builder.sourceware.org/buildbot/#builders/234/builds/22/steps/5/logs/test-suite_log
- 6: prep ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/234/builds/22/steps/6/logs/stdio
- 7: build bunsen.cpio.gz ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/234/builds/22/steps/7/logs/stdio
- 8: fetch bunsen.cpio.gz ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/234/builds/22/steps/8/logs/stdio
- 9: unpack bunsen.cpio.gz ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/234/builds/22/steps/9/logs/stdio
- 10: pass .bunsen.source.gitname ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/234/builds/22/steps/10/logs/stdio
- 11: pass .bunsen.source.gitdescribe ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/234/builds/22/steps/11/logs/stdio
- 12: pass .bunsen.source.gitbranch ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/234/builds/22/steps/12/logs/stdio
- 13: pass .bunsen.source.gitrepo ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/234/builds/22/steps/13/logs/stdio
- 14: upload to bunsen ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/234/builds/22/steps/14/logs/stdio
- 15: clean up ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/234/builds/22/steps/15/logs/stdio
- 16: make distclean ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/234/builds/22/steps/16/logs/stdio
next reply other threads:[~2023-03-02 21:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 21:57 builder [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-06 17:59 builder
2024-05-06 17:27 builder
2024-03-02 1:40 builder
2023-10-02 21:47 builder
2023-09-07 15:48 builder
2023-09-07 15:45 builder
2023-09-07 15:13 builder
[not found] <20230518213228.971653858D39@sourceware.org>
2023-05-18 22:31 ` Mark Wielaard
2023-05-18 21:32 builder
2023-04-14 14:17 builder
2023-04-03 15:24 builder
2023-03-22 17:23 builder
2023-03-02 22:08 builder
2023-03-02 21:57 builder
2023-03-02 21:37 builder
2023-03-02 21:37 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=20230302215759.9DDC73858C83@sourceware.org \
--to=builder@sourceware.org \
--cc=dodji@redhat.com \
--cc=dodji@seketeli.org \
--cc=fred@statdns.com \
--cc=gprocida@google.com \
--cc=guillermo.e.martinez@oracle.com \
--cc=hexiaole@kylinos.cn \
--cc=libabigail@sourceware.org \
--cc=maennich@google.com \
--cc=mark@klomp.org \
--cc=petr.pavlu@suse.com \
--cc=sam@gentoo.org \
--cc=sochat1@llnl.gov \
--cc=vsoch@users.noreply.github.com \
--cc=vvvvvv@google.com \
--cc=woodard@redhat.com \
/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).