From: "serhei at serhei dot io" <sourceware-bugzilla@sourceware.org>
To: bunsen@sourceware.org
Subject: [Bug bunsen/29806] New: enable/document per-project regression analysis settings
Date: Fri, 18 Nov 2022 17:03:59 +0000 [thread overview]
Message-ID: <bug-29806-12167@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29806
Bug ID: 29806
Summary: enable/document per-project regression analysis
settings
Product: bunsen
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: bunsen
Assignee: bunsen at sourceware dot org
Reporter: serhei at serhei dot io
Target Milestone: ---
jemarch's suggestions for configurability in the diff / regression analysis
- status of outcome codes (e.g. is 'UNSUPPORTED' considered a regression?)
- subset of expfiles (e.g. we care about essential-thing.exp but not
weird-flaky-test.exp)
Most analysis settings could be changed by tweaking the scripting. However, as
jemarch points out, this requires either modifying the sourceware bunsen
instance or cloning the bunsendb git repo and running your own analysis. It's
beneficial to have an easy procedure to let the sourceware bunsen-analysis be
tweaked for common settings per-project.
Any other things deserving of easily accessible knobs?
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2022-11-18 17:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-29806-12167@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).