Image reports - default value for start/end build number and tests
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
LAVA Dashboard (deprecated) |
Fix Released
|
High
|
Stevan Radaković |
Bug Description
I'm confused by the default value used for start build number/end build number/tests on the filters section available on image reports. It seems to keep the value selected "previously".
As a result, I should always edit the end build number value and the tests (if new tests have been added).
I expect the following default value:
- end build number is always the latest (you'll have to edit only if you want to check specific range of builds)
- start build number is the latest build number - 15 or 20 (a range of the last 15-20 builds seems reasonable)
- all tests are selected (you'll have to edit only if you want to filter some tests)
Obviously, that's my personal preferences. If there's rationale to current behavior, I'll be glad to hear them.
Related branches
- Senthil Kumaran S: Approve
- Linaro Automation & Validation: Pending requested
-
Diff: 34 lines (+6/-4)1 file modifieddashboard_app/static/dashboard_app/js/image-report.js (+6/-4)
Changed in lava-dashboard: | |
assignee: | nobody → Stevan Radaković (stevanr) |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in lava-dashboard: | |
milestone: | none → 2013.08 |
Changed in lava-dashboard: | |
status: | Triaged → In Progress |
Changed in lava-dashboard: | |
status: | In Progress → Fix Committed |
Changed in lava-dashboard: | |
status: | Fix Committed → Fix Released |
I encountered this issue today looking at the kernel ci builds. Ideally, people will go here every day and determine whether or not a kernel that was booting, no longer boots. With both the Graph and the Data table hiding data, it simply looks like there was no build. (unless someone thinks of looking at the end-number).