Bug 1379681 - [RFE] add phase level details to matrix
Summary: [RFE] add phase level details to matrix
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Beaker
Classification: Retired
Component: web UI
Version: develop
Hardware: Unspecified
OS: Unspecified
low
unspecified vote
Target Milestone: ---
Assignee: beaker-dev-list
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-27 12:45 UTC by Dalibor Pospíšil
Modified: 2020-06-02 11:55 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-02 11:55:13 UTC


Attachments (Terms of Use)

Description Dalibor Pospíšil 2016-09-27 12:45:50 UTC
It would be nice if matrix have got a check box which would enable more details so I could see not only task per line but also phase per line. It would be also beneficial to allow displaying task/phase score.

It would really help to quickly spot regressions even in very complex tasks. E.g. in SELinux we often use tasks with a lot of phases. If there are phases failing on old and new packages it masks regressions in other phases as the overall fail is still the same.

Comment 1 Roman Joost 2016-09-28 05:30:18 UTC
Dear Dalibor,

would you be able to point us to a few examples to get an idea? Cheers!

Comment 2 Dalibor Pospíšil 2016-09-30 07:30:58 UTC
For example here https://beaker.engineering.redhat.com/matrix/?toggle_nacks_on=on&job_ids=1471000+1479064+1479986+1481120+1473958

particularly tasks /CoreOS/selinux-policy/Sanity/sepolicy and /CoreOS/policycoreutils/Sanity/semanage identified regression but it can be seen only by looking at phases score, particularly sepolicy-manpage and fcontext-bz-1122850 respectively.

It would be good to see something like this:

Task                                                         |            aarch64          |           ppc64           |          ppc64le          |           s390x           |          x86_64
                                                             | Server - old  | Server - new| Server - old| Server - new| Server - old| Server - new| Server - old| Server - new| Server - old| Server - new
-------------------------------------------------------------+---------------+-------------+-------------+-------------+-------------+-------------+-------------+-------------+-------------+-------------
/CoreOS/policycoreutils/Sanity/semanage                      |   Fail: 1     | Fail: 2     | Fail: 1     | Fail: 2     | Fail: 1     | Fail: 2     | Fail: 1     | Fail: 2     | Fail: 1     | Fail: 2
/CoreOS/policycoreutils/Sanity/semanage: Setup               |   Pass: 1(0)  | Pass: 2(0)  | Pass: 1(0)  | Pass: 2(0)  | Pass: 1(0)  | Pass: 2(0)  | Pass: 1(0)  | Pass: 2(0)  | Pass: 1(0)  | Pass: 2(0)
/CoreOS/policycoreutils/Sanity/semanage: boolean-bz-1124345  |   Fail: 1(10) | Fail: 2(10) | Fail: 1(10) | Fail: 2(10) | Fail: 1(10) | Fail: 2(10) | Fail: 1(10) | Fail: 2(10) | Fail: 1(10) | Fail: 2(10)
/CoreOS/policycoreutils/Sanity/semanage: fcontext-bz-1122850 |   Fail: 1(29) | Fail: 2(36) | Fail: 1(29) | Fail: 2(36) | Fail: 1(29) | Fail: 2(36) | Fail: 1(29) | Fail: 2(36) | Fail: 1(29) | Fail: 2(36)
/CoreOS/policycoreutils/Sanity/semanage: bz-1122023          |   Fail: 1(2)  | Pass: 2(0)  | Fail: 1(2)  | Pass: 2(0)  | Fail: 1(2)  | Pass: 2(0)  | Fail: 1(2)  | Pass: 2(0)  | Fail: 1(2)  | Pass: 2(0)
/CoreOS/policycoreutils/Sanity/semanage: Cleanup             |   Pass: 1(0)  | Pass: 2(0)  | Pass: 1(0)  | Pass: 2(0)  | Pass: 1(0)  | Pass: 2(0)  | Pass: 1(0)  | Pass: 2(0)  | Pass: 1(0)  | Pass: 2(0)

the numbers in brackets would be maximum of the phase's score across all relevant instances. Also it would be nice to highlight the changes better->worse and vice versa1 by colors.

Comment 4 Roman Joost 2016-10-03 22:40:53 UTC
Thanks Dalibor!

Might be interesting to do a spike of implementing it in the current matrix. I'm worried that it might make it slower than it already is.

Comment 5 Martin Styk 2020-06-02 11:55:13 UTC
Hello,

thank you for opening issue in Beaker project.
This issue was marked with component "web ui".
As we are not planning to address any further issues in current UI, due to technical stack and not being able to work with Python 3 codebase, I'm closing this issue as WONTFIX.
New UI will be reimplemented within new versions of Beaker.

If you have any questions feel free to reach out to me.

Best regards,
Martin <martin.styk>


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