From: Khem Raj <raj.khem@gmail.com>
To: Mark Wielaard <mark@klomp.org>
Cc: elfutils-devel@sourceware.org
Subject: Re: ☠ Buildbot (Sourceware): elfutils-snapshots-coverage - failed test (failure) (main)
Date: Mon, 11 Mar 2024 07:05:53 -0700 [thread overview]
Message-ID: <CAMKF1spYfvUD0wKCYeXGZib-=vhjaSLMiGyn0R5xxNJS87egdg@mail.gmail.com> (raw)
In-Reply-To: <e952bce0370c13365b76c1cd6b9444db701eae97.camel@klomp.org>
On Mon, Mar 11, 2024 at 4:23 AM Mark Wielaard <mark@klomp.org> wrote:
>
> Hi Khem,
>
> On Mon, 2024-03-11 at 02:33 +0000, builder@sourceware.org wrote:
> > A new failure has been detected on builder elfutils-snapshots-coverage while building elfutils.
> >
> > Full details are available at:
> > https://builder.sourceware.org/buildbot/#/builders/250/builds/105
> >
> > Build state: failed test (failure)
> > Revision: d74f4c1d572fbeb7454a2ffa02cbc955ea24780d
> > Worker: snapshots
> > Build Reason: (unknown)
> > Blamelist: Khem Raj <raj.khem@gmail.com>
> >
> > Steps:
> >
> > - 0: worker_preparation ( success )
> >
> > - 1: git checkout ( success )
> > Logs:
> > - stdio: https://builder.sourceware.org/buildbot/#/builders/250/builds/105/steps/1/logs/stdio
> >
> > - 2: autoreconf ( success )
> > Logs:
> > - stdio: https://builder.sourceware.org/buildbot/#/builders/250/builds/105/steps/2/logs/stdio
> >
> > - 3: configure ( success )
> > Logs:
> > - stdio: https://builder.sourceware.org/buildbot/#/builders/250/builds/105/steps/3/logs/stdio
> > - config.log: https://builder.sourceware.org/buildbot/#/builders/250/builds/105/steps/3/logs/config_log
> >
> > - 4: make ( warnings )
> > Logs:
> > - stdio: https://builder.sourceware.org/buildbot/#/builders/250/builds/105/steps/4/logs/stdio
> > - warnings (3): https://builder.sourceware.org/buildbot/#/builders/250/builds/105/steps/4/logs/warnings__3_
> >
> > - 5: make check ( failure )
> > Logs:
> > - stdio: https://builder.sourceware.org/buildbot/#/builders/250/builds/105/steps/5/logs/stdio
> > - test-suite.log: https://builder.sourceware.org/buildbot/#/builders/250/builds/105/steps/5/logs/test-suite_log
>
> That was clearly not your fault. There seems to be a space missing in
> the make -kcheck command (after the -k). I'll go look in the builder
> sources where that came from.
Thanks Mark !
>
> Cheers,
>
> Mark
next prev parent reply other threads:[~2024-03-11 14:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 2:33 builder
2024-03-11 11:23 ` Mark Wielaard
2024-03-11 14:05 ` Khem Raj [this message]
2024-03-11 14:53 ` Mark Wielaard
2024-03-27 14:07 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='CAMKF1spYfvUD0wKCYeXGZib-=vhjaSLMiGyn0R5xxNJS87egdg@mail.gmail.com' \
--to=raj.khem@gmail.com \
--cc=elfutils-devel@sourceware.org \
--cc=mark@klomp.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).