public inbox for libc-testresults@sourceware.org
help / color / mirror / Atom feed
From: builder@sourceware.org
To: "Adhemerval Zanella" <adhemerval.zanella@linaro.org>,
	"Aurelien Jarno" <aurelien@aurel32.net>,
	"Carlos O'Donell" <carlos@redhat.com>,
	"Florian Weimer" <fweimer@redhat.com>,
	"H.J. Lu" <hjl.tools@gmail.com>,
	"Samuel Thibault" <samuel.thibault@ens-lyon.org>,
	"Wilco Dijkstra" <wilco.dijkstra@arm.com>,
	caiyinyu <caiyinyu@loongson.cn>
Cc: libc-testresults@sourceware.org
Subject: ☠ Buildbot (Sourceware): glibc-snapshots-trunk - failed compile (failure) (master)
Date: Thu, 25 Apr 2024 12:21:41 +0000	[thread overview]
Message-ID: <20240425122141.E583C3846410@sourceware.org> (raw)

A new failure has been detected on builder glibc-snapshots-trunk while building glibc.

Full details are available at:
    https://builder.sourceware.org/buildbot/#/builders/264/builds/382

Build state: failed compile (failure)
Revision: 3a3a4497421422aa854c855cbe5110ca7d598ffc
Worker: snapshots
Build Reason: (unknown)
Blamelist: Adhemerval Zanella <adhemerval.zanella@linaro.org>, Aurelien Jarno <aurelien@aurel32.net>, Carlos O'Donell <carlos@redhat.com>, Florian Weimer <fweimer@redhat.com>, H.J. Lu <hjl.tools@gmail.com>, Samuel Thibault <samuel.thibault@ens-lyon.org>, Wilco Dijkstra <wilco.dijkstra@arm.com>, caiyinyu <caiyinyu@loongson.cn>

Steps:

- 0: worker_preparation ( success )

- 1: git checkout ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/264/builds/382/steps/1/logs/stdio

- 2: rm -rf glibc-build ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/264/builds/382/steps/2/logs/stdio

- 3: configure ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/264/builds/382/steps/3/logs/stdio
        - config.log: https://builder.sourceware.org/buildbot/#/builders/264/builds/382/steps/3/logs/config_log

- 4: make dist ( failure )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/264/builds/382/steps/4/logs/stdio


                 reply	other threads:[~2024-04-25 12:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240425122141.E583C3846410@sourceware.org \
    --to=builder@sourceware.org \
    --cc=adhemerval.zanella@linaro.org \
    --cc=aurelien@aurel32.net \
    --cc=caiyinyu@loongson.cn \
    --cc=carlos@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=hjl.tools@gmail.com \
    --cc=libc-testresults@sourceware.org \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=wilco.dijkstra@arm.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).