From: Mark Wielaard <mark@klomp.org>
To: libc-alpha@sourceware.org
Cc: buildbot@sourceware.org
Subject: Re: glibc builder.sourceware.org integration
Date: Sat, 2 Jul 2022 00:24:44 +0200 [thread overview]
Message-ID: <Yr90LLGDDStKGjUG@wildebeest.org> (raw)
In-Reply-To: <Yr7h6mb1V9gtYT85@wildebeest.org>
Hi,
On Fri, Jul 01, 2022 at 02:00:42PM +0200, Mark Wielaard wrote:
> For now I have added a make subdirs=elf -jncpus check step. This
> seems to have a couple of hundred tests which should be quick enough
> to run on all builders. Test results are uploaded to the bunsendb for
> comparison between distr/arches. Builders all seem to be green (except
> for the full testrun builders of course), but the glibc-fedora-ppc64le builder has one FAIL:
> FAIL: elf/tst-ldconfig-bad-aux-cache
> https://builder.sourceware.org/buildbot/#/builders?tags=glibc
> https://builder.sourceware.org/buildbot/#/builders/127/builds/35
>
> Frank, I cannot find the corresponding bunsen test results for that
> build under https://builder.sourceware.org/testruns/ did I make a
> mistake in the bunsen upload step?
It is there now. I don't know why it wasn't there earlier. Frank, is
there a delay between the bunsendb update and when the testruns show
up?
https://builder.sourceware.org/testrun/deda118447159c9affe00348cfb1ddf667563fe4
Which also contains the st-ldconfig-bad-aux-cache.out file
https://builder.sourceware.org/testrun/deda118447159c9affe00348cfb1ddf667563fe4?filename=elf%2Ftst-ldconfig-bad-aux-cache.out
Timed out: killed the child process
I couldn't immediately replicate that on a ppc64le setup.
Lets see if a next build also causes this test to time out.
Cheers,
Mark
next prev parent reply other threads:[~2022-07-01 22:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-26 22:23 Mark Wielaard
2022-07-01 12:00 ` Mark Wielaard
2022-07-01 22:24 ` Mark Wielaard [this message]
2022-07-02 1:09 ` Frank Ch. Eigler
2022-07-02 19:45 ` Mark Wielaard
2022-07-03 15:22 ` Dorian ROSSE
2022-07-03 16:37 ` Mark Wielaard
2022-07-04 15: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=Yr90LLGDDStKGjUG@wildebeest.org \
--to=mark@klomp.org \
--cc=buildbot@sourceware.org \
--cc=libc-alpha@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).