Bug 6686

Summary: cpu_usage value null for tasks with outcome=0
Product: [Build System, Metadata & Runtime] Toaster Reporter: Ionut Chisanovici <ionutx.chisanovici>
Component: toasterAssignee: Alexandru Damian <alexandru.damian>
Status: VERIFIED FIXED QA Contact: Ionut Chisanovici <ionutx.chisanovici>
Severity: normal    
Priority: Undecided CC: alexandru.damian, belen.barros.pena, cristiana.voicu
Version: 1.7   
Target Milestone: ---   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Ionut Chisanovici 2014-09-05 08:34:42 UTC 
Hi,

BUILD: 1.7_M3_RC1: a44006262cf3b810ec78b4cccd8076102a7a0f3e

The value of the elapsed_time field for certain tasks having outcome=0 is null.
See below:

sqlite> select * from orm_task where id=6307;
          build_id = 2
    work_directory = 
         cpu_usage = 
     task_executed = 0
           disk_io = 
       line_number = 0
path_to_sstate_obj = 
   sstate_checksum = 2fbdfa62c7c41855b68649db32dddf2b
        source_url = 
             order = 753
      elapsed_time = 1.02
           logfile = /home/ionut/work/weekly/poky/build/tmp/work/x86_64-linux/gdbm-native/1.11-r0/temp/log.do_install.29549
         recipe_id = 190
         task_name = do_install
           message = recipe gdbm-native-1.11-r0: task do_install: Succeeded
           outcome = 1
                id = 6307
     sstate_result = 0
       script_type = 3

Cheers,
Ionut C
Comment 1 Ionut Chisanovici 2014-09-05 08:39:59 UTC 
Closing this one as the task outcome is 1.

Regards,
Ionut C
Comment 2 Ionut Chisanovici 2014-09-05 08:40:15 UTC 
Verified.