Bug 604517 - RFE: filtering of matrix report - display only lines where results differ or regressions
RFE: filtering of matrix report - display only lines where results differ or ...
Status: NEW
Product: Beaker
Classification: Community
Component: web UI (Show other bugs)
0.5
All Linux
low Severity medium (vote)
: ---
: ---
Assigned To: beaker-dev-list
UX
: FutureFeature, Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-06-16 02:37 EDT by Marian Csontos
Modified: 2016-05-26 09:25 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Marian Csontos 2010-06-16 02:37:03 EDT
Description of problem:
I have a job with about 100 tasks (this applies to all TierN tests).
Matrix is great for reviewing regressions but 90%+ of the results are the same.

See: https://beaker.engineering.redhat.com/matrix/?whiteboard_filter=&job_ids=3229

I would like to be able to see only lines where:
- the results are not same
- the result is worse than base result

I run as two recipesets in single job.
It might be tricky, how to specify what's the base and what its update...
Comment 1 Marian Csontos 2010-06-16 02:39:46 EDT
See also Bug 596410 requesting filtering of columns.

This would add filter for rows as well...
Comment 2 Raymond Mancy 2010-06-16 03:09:15 EDT
(In reply to comment #0)
> Description of problem:
> I have a job with about 100 tasks (this applies to all TierN tests).
> Matrix is great for reviewing regressions but 90%+ of the results are the same.
> 
> See:
> https://beaker.engineering.redhat.com/matrix/?whiteboard_filter=&job_ids=3229
> 
> I would like to be able to see only lines where:
> - the results are not same
> - the result is worse than base result
> 
> I run as two recipesets in single job.
> It might be tricky, how to specify what's the base and what its update...    

You wouldn't really design it on the recipeset level, that would only work for people who have set up their Jobs to work in such a way, and I assume most don't.

Perhaps a 1:N relationship could be created on jobs, and then a special kind of matrix report could be run on these, which would basically do a complement of the base against all the other 'non base' jobs?
Comment 3 Marian Csontos 2010-06-16 04:30:58 EDT
> You wouldn't really design it on the recipeset level, that would only work for
> people who have set up their Jobs to work in such a way, and I assume most
> don't.

You are right of course. It was just convenient having it in one job as I need to rerun it... :-(

More info:

Display/Hide should be done with javascript - so one does not have to reload results. Rationale: Bug 604541 I just added...

Note You need to log in before you can comment on or make changes to this bug.