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
Also appears in 1.8 M2 RC2, commit: 22c38e2d8a058619e3d05534b5e830b750aa4241
Also appears in 1.8_M3.RC1, commit: 40d80f9e019118ac7bcd268f21e350bc154a4a63 Cheers, Ionut C
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.
Replaced with 7594, which tracks what's causing this problem. *** This bug has been marked as a duplicate of bug 7594 ***
Verified.