From: "me at serhei dot io" <sourceware-bugzilla@sourceware.org>
To: bunsen@sourceware.org
Subject: [Bug bunsen/25091] [v1.0] analysis: which regressions are truly new?
Date: Wed, 01 Jan 2020 00:00:00 -0000 [thread overview]
Message-ID: <bug-25091-12167-S1Wv6z72Eu@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25091-12167@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25091
--- Comment #2 from Serhei Makarov <me at serhei dot io> ---
Figuring out how to cache the +new_regressions analysis in a reasonable way.
The problem is that +new_regressions can be run with different key=* and
window_size/novelty_threshold=* arguments. So the cached data must be stored in
a way that allows recomputation if necessary.
My current thought is to store
- list of single_change: (name, subtest, outcome_pair)
- map of commit_pair -> list of key or '*'
- map of commit_pair -> list of (index of) single_change
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2020-01-15 19:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 [Bug bunsen/25091] New: " 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 [this message]
2022-09-16 17:15 ` [Bug bunsen/25091] " serhei at serhei dot io
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-S1Wv6z72Eu@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).