Bug 7200

Summary: cpu_usage value for some tasks doesn't match the value in the stats file
Product: [Build System, Metadata & Runtime] Toaster Reporter: Ionut Chisanovici <ionutx.chisanovici>
Component: toasterAssignee: Alexandru Damian <alexandru.damian>
Status: VERIFIED DUPLICATE QA Contact: Alexandru Roman <alexandru.costinx.roman>
Severity: normal    
Priority: Medium CC: alexandru.costinx.roman, alexandru.damian, belen.barros.pena, bluelightning, bogdanx.a.voiculescu, cristiana.voicu
Version: 1.8   
Target Milestone: 1.8 M3   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: Regression (Used to work)
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
toaster.sqlite none

Description Ionut Chisanovici 2015-01-20 13:45:03 UTC
Created attachment 2343 [details]
toaster.sqlite

Hi,

The cpu_usage value in orm_task table for some tasks doesn't match the value in the stats file:

BUILD: 1.8_M2.rc1: d9d5b8b499af3ae01a1e33d0d3969c54c2d4ab1b

sqlite> select * from orm_task where id=4966;
          build_id = 1
    work_directory = 
         cpu_usage = 0.1
     task_executed = 1
           disk_io = 92
       line_number = 0
path_to_sstate_obj = 
   sstate_checksum = 176b434b9b3e83181a9eb1d621b75dd3
        source_url = 
             order = 703
      elapsed_time = 2.91
           logfile = /home/ionut/work/poky_1.8/poky/build/tmp/work/x86_64-linux/python-pygobject-native/2.28.3-r0/temp/log.do_fetch.16566
         recipe_id = 308
         task_name = do_fetch
           message = recipe python-pygobject-native-2.28.3-r0: task do_fetch: Succeeded
           outcome = 0
                id = 4966
     sstate_result = 0
       script_type = 2

$ grep 'CPU usage:' tmp/buildstats/core-image-sato-qemux86/201501201304/python-pygobject-native-2.28.3-r0/do_fetch 
CPU usage: 0.2% 

Toaster sqlite db attached.

Cheers,
Ionut C
Comment 1 Ionut Chisanovici 2015-02-03 14:46:23 UTC
Also appears in 1.8 M2 RC2, commit: 22c38e2d8a058619e3d05534b5e830b750aa4241
Comment 2 Ionut Chisanovici 2015-02-26 13:57:32 UTC
Also appears in 1.8_M3.RC1, commit: 40d80f9e019118ac7bcd268f21e350bc154a4a63.

Cheers,
Ionut C
Comment 3 Belen Barros Pena 2015-03-11 16:32:32 UTC
the system some times gets confused between native / non-native tasks and we cannot reliable detect which task is which. Luckily it happens very rarely, so it is too much effort for little gain.
Comment 4 Belen Barros Pena 2015-04-10 14:39:39 UTC
Replaced with 7594, which tracks what's causing this problem.

*** This bug has been marked as a duplicate of bug 7594 ***
Comment 5 Alexandru Roman 2015-11-19 09:37:45 UTC
Verified.