From: "Frank Ch. Eigler" <fche@elastic.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: Mark Wielaard <mark@klomp.org>,
Thomas Fitzsimmons <fitzsim@fitzsim.org>,
'GNU C Library' <libc-alpha@sourceware.org>,
Wilco Dijkstra <Wilco.Dijkstra@arm.com>
Subject: Re: [PATCH] Improve performance of IO locks
Date: Mon, 22 Aug 2022 10:58:44 -0400 [thread overview]
Message-ID: <YwOZpOhfrlzhf/XU@elastic.org> (raw)
In-Reply-To: <871qt81snr.fsf@oldenburg.str.redhat.com>
Hi -
> > Another is to look at all results for a particular builder (as above)
> > or to look at all the glibc builds using the (sql) search form. e.g.
> > https://builder.sourceware.org/testruns/?has_keyvalue_like_k=testrun.git_describe&has_keyvalue_like_v=%25glibc%25
>
> Thank you for these links, they surely look useful. I assume the zebra
> pattern in the table is not actually meaningful (it's too regular for
> that), it's just to improve readability, right?
Correct.
> What confuses me still is that the run lists do not seem to have numbers
> with failure counts.
Yes, while one can view fail/etc. counts of all the test cases in one
testrun [https://tinyurl.com/mry25ekt], there is no single view that
contrasts such counts for multiple runs. It's coming.
- FChE
next prev parent reply other threads:[~2022-08-22 14:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 16:32 Wilco Dijkstra
2022-08-01 11:06 ` Wilco Dijkstra
2022-08-07 12:51 ` Cristian Rodríguez
2022-08-15 22:27 ` Mark Wielaard
2022-08-16 3:07 ` Thomas Fitzsimmons
2022-08-16 7:31 ` Florian Weimer
2022-08-16 10:00 ` Mark Wielaard
2022-08-16 10:08 ` Florian Weimer
2022-08-17 13:45 ` Mark Wielaard
2022-08-22 10:25 ` Florian Weimer
2022-08-22 14:58 ` Frank Ch. Eigler [this message]
2022-08-16 11:19 ` Andreas Schwab
2022-08-16 10:24 ` Wilco Dijkstra
2022-08-16 13:18 ` Thomas Fitzsimmons
2022-08-16 14:31 ` Thomas Fitzsimmons
2022-08-17 11:53 ` 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=YwOZpOhfrlzhf/XU@elastic.org \
--to=fche@elastic.org \
--cc=Wilco.Dijkstra@arm.com \
--cc=fitzsim@fitzsim.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@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).