Bug 4275

Summary: View a table with all the tasks run for a build
Product: [Build System, Metadata & Runtime] Toaster Reporter: Belen Barros Pena <belen.barros.pena>
Component: toasterAssignee: Ravi Chintakunta <ravi.chintakunta>
Status: VERIFIED FIXED QA Contact: Ionut Chisanovici <ionutx.chisanovici>
Severity: enhancement    
Priority: Medium+ CC: alexandru.damian, bogdanx.a.voiculescu, calinx.l.dragomir, david.reyna, ionutx.chisanovici, jessica.zhang, ravi.chintakunta
Version: unspecified   
Target Milestone: 1.6 M2   
Hardware: All   
OS: Multiple   
Whiteboard: GUI design available
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
Tasks information set
none
Tasks information set
none
Tasks information set
none
Tasks information set
none
Tasks information set
none
IA 1.2 All tasks
none
Tasks information
none
Tasks information
none
Design 1.2 All tasks
none
Design 1.2 All tasks
none
IA 1.2 All tasks
none
Design 1.2 All tasks
none
IA 1.2 All tasks
none
Tasks information
none
Design 1.2 All tasks
none
IA 1.2 All tasks
none
Design 1.2 All tasks
none
Design 1.2 All tasks
none
Design 1.2 All tasks
none
IA 1.3 All tasks
none
Design 1.3 All tasks
none
Design 1.3 All tasks
none
Design 1.3 All tasks
none
Design 1.3 All tasks
none
Design 1.3 All tasks none

Description Belen Barros Pena 2013-04-12 11:08:36 UTC
For each task I will see some basic information, such as:

* Task name
* Recipe
* Path to log file
* Issues / errors thrown 

etc. The complete information set is TBC.

For an idea of this feature, check:

http://www.yoctoproject.org/webhob/phase3_final_web_prototype/project-build-tasks.html
Comment 1 Belen Barros Pena 2013-05-29 15:34:52 UTC
Created attachment 1229 [details]
Tasks information set

It looks like the initial set of information for tasks includes:

* Task type (sstate or built)
* Task outcome
* sstate checksum
* Path searched to sstate object
* Recipe name
* Task naem
* Source URL(s)
* Log file
* Work directory
* Python / shell 
* Code
* Python stack trace
* Overall space usage
* Disk I/O
* CPU usage
* Time
* Dependent tasks
* Precursor tasks
* Number of errors
* Number of warnings
* Error content
* Warning content

I have quite a few questions about the above list, which I have included in the attached spreadsheet. Help answering them would be really appreciated.
Comment 2 Belen Barros Pena 2013-05-31 11:46:26 UTC
Created attachment 1232 [details]
Tasks information set

I've managed to gather answers to most of the questions related to task information. All answers and the updated information set are in the attached spreadsheet. The only question pending relates to how to report Disk I/O information for a task. We need to bring this one to RP.

As things stand, the task table requested by this bug will have the following columns:

* Task type
* Outcome
* Recipe name
* Task name
* Log file
* Work directory
* CPU usage
* Time
* Order
* Number of errors
* Number of warnings

Which columns will display by default and in which order is TBD.
Comment 3 Belen Barros Pena 2013-06-03 11:54:04 UTC
Created attachment 1234 [details]
Tasks information set

Thanks to Beth Flanagan we have come up with a measure of Disk I/O for tasks: number of ms spent doing I/Os. I've updated the attached file accordingly. 

With this, the task table requested by this bug will have the following columns:

* Task type
* Outcome
* Recipe name
* Task name
* Log file
* Work directory
* CPU usage
* Disk I/O
* Time
* Order
* Number of errors
* Number of warnings

Which columns will display by default and in which order is TBD.
Comment 4 Belen Barros Pena 2013-06-05 10:47:11 UTC
Created attachment 1240 [details]
Tasks information set
Comment 5 Belen Barros Pena 2013-06-07 11:30:27 UTC
Created attachment 1247 [details]
Tasks information set
Comment 6 Belen Barros Pena 2013-06-07 15:10:17 UTC
Created attachment 1251 [details]
IA 1.2 All tasks
Comment 7 Belen Barros Pena 2013-06-11 12:42:22 UTC
Created attachment 1262 [details]
Tasks information
Comment 8 Belen Barros Pena 2013-06-11 14:31:22 UTC
Created attachment 1265 [details]
Tasks information
Comment 9 Belen Barros Pena 2013-07-02 09:49:04 UTC
Created attachment 1298 [details]
Design 1.2 All tasks
Comment 10 Belen Barros Pena 2013-07-03 10:12:51 UTC
Created attachment 1299 [details]
Design 1.2 All tasks
Comment 11 Belen Barros Pena 2013-07-05 11:20:50 UTC
Created attachment 1312 [details]
IA 1.2 All tasks
Comment 12 Belen Barros Pena 2013-07-05 11:21:18 UTC
Created attachment 1313 [details]
Design 1.2 All tasks
Comment 13 Belen Barros Pena 2013-07-11 10:49:07 UTC
Moving to M3 as part of milestone reallocation and as discussed with Alex
Comment 14 Belen Barros Pena 2013-07-12 16:29:26 UTC
Created attachment 1327 [details]
IA 1.2 All tasks
Comment 15 Belen Barros Pena 2013-07-12 16:30:21 UTC
Created attachment 1328 [details]
Tasks information
Comment 16 Belen Barros Pena 2013-07-15 11:26:06 UTC
Created attachment 1331 [details]
Design 1.2 All tasks
Comment 17 Belen Barros Pena 2013-07-19 13:13:42 UTC
Created attachment 1343 [details]
IA 1.2 All tasks
Comment 18 Belen Barros Pena 2013-07-19 13:14:00 UTC
Created attachment 1344 [details]
Design 1.2 All tasks
Comment 19 Belen Barros Pena 2013-07-31 10:15:46 UTC
Created attachment 1393 [details]
Design 1.2 All tasks
Comment 20 Belen Barros Pena 2013-08-02 10:27:17 UTC
Created attachment 1400 [details]
Design 1.2 All tasks
Comment 21 Alexandru Damian 2013-08-09 11:06:56 UTC
All needed information is available in the database.
Comment 22 Belen Barros Pena 2013-09-09 10:42:25 UTC
Created attachment 1472 [details]
IA 1.3 All tasks
Comment 23 Belen Barros Pena 2013-09-09 10:43:05 UTC
Created attachment 1473 [details]
Design 1.3 All tasks
Comment 24 Belen Barros Pena 2013-09-09 13:06:39 UTC
Created attachment 1477 [details]
Design 1.3 All tasks
Comment 25 Belen Barros Pena 2013-12-31 12:16:42 UTC
Created attachment 1701 [details]
Design 1.3 All tasks
Comment 26 Ravi Chintakunta 2014-01-07 16:31:42 UTC
Ravi Chintakunta is working on this.
Comment 27 Belen Barros Pena 2014-01-13 14:27:10 UTC
Created attachment 1714 [details]
Design 1.3 All tasks

We have changed the default sorting for the tasks from Recipe to Order, so that tasks are now sorted by their execution sequence. The default ordering criteria should always be part of the minimum table, so that we can revert the table to the default ordering without worrying about the state of the 'Edit columns' menu. Therefore, I've added the "Order" column to the minimum table (see page 7 of the document "Design 1.3 All tasks")
Comment 28 Belen Barros Pena 2014-02-14 16:39:51 UTC
Created attachment 1773 [details]
Design 1.3 All tasks

The team has concluded that Cached tasks should be grouped with the Not executed tasks, instead of the Executed tasks. Updating the design document accordingly.
Comment 29 Ionut Chisanovici 2014-10-09 12:52:00 UTC
This is verified.

Cheers,
Ionut C