Bug 7201

Summary: elapsed_time value in task table doesn't match sometime the value in the task 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:57:56 UTC
Created attachment 2344 [details]
toaster.sqlite

Hi,

BUILD: 1.8_M2.rc1: d9d5b8b499af3ae01a1e33d0d3969c54c2d4ab1b

Elapsed_time value in database doesn't match sometime the value in the task stats file:

sqlite> select * from orm_task where id=5050;
          build_id = 1
    work_directory = 
         cpu_usage = 0.1
     task_executed = 1
           disk_io = 5472
       line_number = 0
path_to_sstate_obj = 
   sstate_checksum = 19c0637690c04fc53490efa01e9711d0
        source_url = 
             order = 39
      elapsed_time = 141.99
           logfile = /home/ionut/work/poky_1.8/poky/build/tmp/work/i586-poky-linux/glibc-initial/2.20-r0/temp/log.do_fetch.7161
         recipe_id = 59
         task_name = do_fetch
           message = recipe glibc-initial-2.20-r0: task do_fetch: Succeeded
           outcome = 0
                id = 5050
     sstate_result = 0
       script_type = 2

$ grep Elapsed tmp/buildstats/core-image-sato-qemux86/201501201304/glibc-initial-2.20-r0/do_fetch 
glibc-initial-2.20-r0: do_fetch: Elapsed time: 141.98 seconds

Attached toaster sqlite db.

This is happening for a lot of tasks.

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

Cheers,
Ionut C
Comment 3 Belen Barros Pena 2015-03-11 16:32:23 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:18 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-17 16:04:09 UTC
Verified.