| Summary: | Incorrect performance tables if Edit Column drop down is used | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Toaster | Reporter: | Awais <awais_belal> |
| Component: | toaster | Assignee: | David Reyna <david.reyna> |
| Status: | ACCEPTED --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | jessica.zhang, stanciux.mihail |
| Version: | unspecified | ||
| Target Milestone: | 5.99 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
| Attachments: | |||
|
Description
Awais
2017-08-30 12:47:09 UTC
Created attachment 3962 [details]
The table for build time displayed normally
Created attachment 3963 [details]
The table for disk io displayed normally
Created attachment 3964 [details]
Disk IO table edited using Edit columns to show recipe version
Created attachment 3965 [details]
Build time table now misbehaving
I have done some investigation. The problem is that if the user edits the columns for any of these pages, ALL pages get that new set. While it is easy to reset the columns to see any desired data, the user does lose the distinction and value between the three pages. Here are the default column headings for the three performance tables: Time: Task,Recipe,Executed,Outcome,Time (secs) CPU: Task,Recipe,Executed,Outcome,System CPU time (secs),User CPU time (secs) DiskIO: Task,Recipe,Executed,Outcome,Disk I/O (ms) I expect that this issue was introduced with the new Toaster Tables, and that the column caching is not working as expected per page. That data was originally stored in page-specific cookies - I have to investigate how it was changed. I will fix this in YP-2.5 so that YP-2.4 is not made unstable. Bulk move from 4.99 or 0.00 to 5.99 |