Bug 5220 - [webhob-poky/master] sstate_result in tasks table returns always '0' (not applicable)
Summary: [webhob-poky/master] sstate_result in tasks table returns always '0' (not app...
Status: VERIFIED FIXED
Alias: None
Product: Toaster
Classification: Build System, Metadata & Runtime
Component: toaster (show other bugs)
Version: 1.5
Hardware: All Multiple
: Medium normal
Target Milestone: 1.6 M1
Assignee: Cristiana Voicu
QA Contact:
URL:
Whiteboard: toasterui
Depends on:
Blocks:
 
Reported: 2013-09-17 16:30 UTC by Belen Barros Pena
Modified: 2016-05-17 02:58 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Belen Barros Pena 2013-09-17 16:30:23 UTC
'0' (not applicable) is not a valid sstate_result for tasks with outcome '2' (sstate), which should return '3' (restored), '2' (failed) or '1' (missed). 

Below is an example of a task with outcome '2' showing sstate_result '0':

{\"work_directory\": null, \"log_file\": \"\", \"task_executed\": false, \"disk_io\": null, \"line_number\": 0, \"path_to_sstate_obj\": \"\", \"sstate_checksum\": null, \"recipe\": 736, \"sstate_result\": 0, \"source_url\": null, \"elapsed_time\": \"0\", \"py_stack_trace\": null, \"logfile\": null, \"cpu_usage\": null, \"build\": 11, \"task_name\": \"do_populate_sysroot\", \"message\": \"\", \"outcome\": 2, \"order\": 436, \"script_type\": 0}}
Comment 1 Cristiana Voicu 2013-11-18 07:53:01 UTC
the patch was merged to master 
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=51084379d43a6b6bbf828d2adaaccf803e9da081

waiting to be merged on dora-toaster,too, to change the status to resolved
Comment 3 Belen Barros Pena 2013-11-18 16:35:57 UTC
verified in 

master:d7ccfc7605f1eb61511b1b2b8db4ac689ce6a468 

and 

dora-toaster:1182665de0da9a6e5fc77107f32a7fc1515029d0
Comment 4 Robert Yang 2016-05-17 02:58:28 UTC
*** Bug 9429 has been marked as a duplicate of this bug. ***