Bug 29806 - enable/document per-project regression analysis settings
Summary: enable/document per-project regression analysis settings
Status: NEW
Alias: None
Product: bunsen
Classification: Unclassified
Component: bunsen (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: bunsen developer list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-11-18 17:03 UTC by Serhei Makarov
Modified: 2022-11-18 17:03 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Serhei Makarov 2022-11-18 17:03:59 UTC 
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?