From: "serhei at serhei dot io" <sourceware-bugzilla@sourceware.org>
To: bunsen@sourceware.org
Subject: [Bug bunsen/25091] analysis: which regressions are truly new?
Date: Fri, 16 Sep 2022 17:15:34 +0000 [thread overview]
Message-ID: <bug-25091-12167-ClgIV3T9wp@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25091-12167@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25091
Serhei Makarov <serhei at serhei dot io> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|bunsen at sourceware dot org |serhei at serhei dot io
Summary|[v1.0] analysis: which |analysis: which regressions
|regressions are truly new? |are truly new?
--- Comment #3 from Serhei Makarov <serhei at serhei dot io> ---
I did a lot of experimentation with the regression-filtering view on the
prototype branch earlier this spring, but it's still far from perfect in terms
of accurate & easy-to-read results. Eventually I will try implementing
something similar to the prototype/2022:scripts_main/show_changes*.py scripts
on the new master branch, so this PR is still relevant going forward.
For the time being the 'best practice' for getting an overview of regressions
is to generate a set of grid views with R-show-testcases ( / show_testcases.py
), grab a coffee, and page through the results.
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2022-09-16 17:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 [Bug bunsen/25091] New: [v1.0] " me at serhei dot io
2019-01-01 0:00 ` [Bug bunsen/25091] " me at serhei dot io
2020-01-01 0:00 ` me at serhei dot io
2022-09-16 17:15 ` serhei at serhei dot io [this message]
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=bug-25091-12167-ClgIV3T9wp@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=bunsen@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).