Bug 9498 - Progress bar not behaving correctly on mysql
Summary: Progress bar not behaving correctly on mysql
Status: RESOLVED FIXED
Alias: None
Product: Toaster
Classification: Build System, Metadata & Runtime
Component: toaster (show other bugs)
Version: 2.2
Hardware: x86 Multiple
: Medium normal
Target Milestone: 2.2
Assignee: Elliot Smith
QA Contact: Libertad
URL:
Whiteboard:
Depends on: 9631
Blocks:
  Show dependency tree
 
Reported: 2016-04-21 11:36 UTC by Michael Wood
Modified: 2016-07-19 10:51 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

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 Michael Wood 2016-04-21 11:36:05 UTC 
Progress bar doesn't behave correctly on Mysql as the status properties aren't being translated into their strings, we're just getting an int for the enum value, which confuses the js.
Comment 1 brian avery 2016-04-27 15:20:07 UTC 
we should also try to readd the state transitions.  clone, parse, etc.
Comment 2 Belen Barros Pena 2016-04-27 15:28:28 UTC 
What Brian says and also:

This needs design: we should consider showing the tasks currently being executed like in Knotty. 

Josh also suggests:"even listing "x of y tasks complete" might help?"
Comment 3 Elliot Smith 2016-05-13 09:54:22 UTC 
Please raise an enhancement for the additional/changed functionality.

I am going to attempt to fix the bug for now.
Comment 4 Elliot Smith 2016-05-13 10:51:44 UTC 
Updated estimate to reflect just fixing the MySQL issue, i.e. making progress bars behave when using the MySQL back-end.

Patch for this part of the issue submitted to mailing list for review:
https://lists.yoctoproject.org/pipermail/toaster/2016-May/004596.html
Comment 5 Elliot Smith 2016-07-19 10:51:09 UTC 
Libertad: to test:

1. Set up Toaster using MySQL as the database back-end.
2. Start a build.
3. Check that the progress bars update correctly.

Note that the patches for bug 9631 completely rewrite the progress bar functionality, which may affect this issue. I added a dependency on that issue to track the relationship.