Created attachment 1600 [details] gcc-cross-tasks-coming-as-noexec.png There seems to be way too many tasks reported as 'noexec'. For example, for gcc-cross, the following tasks should be 'noexec' tasks: meta/recipes-devtools/gcc/gcc-cross.inc:do_package[noexec] = "1" meta/recipes-devtools/gcc/gcc-cross.inc:do_packagedata[noexec] = "1" meta/recipes-devtools/gcc/gcc-cross.inc:do_package_write_ipk[noexec] = "1" meta/recipes-devtools/gcc/gcc-cross.inc:do_package_write_rpm[noexec] = "1" meta/recipes-devtools/gcc/gcc-cross.inc:do_package_write_deb[noexec] = "1" However, as you can see in the attached screenshot, do_fetch, do_unpack, do_patch, do_configure, do_compile, do_install and do_populate_sysroot are also being reported as 'noexec'. Found in dora-toaster:46814c99eed399b6dd9ff9e83260fefe79c23ec8
All tasks that are not executed are by default NoExec. The script type field should always be interpreted in relation with the task type field. I'm not sure what the expected behaviour is.
We sorted this out as part of bug 5327 executed - noexec will have the script_type set to noexec covered / prebuilt - noexec will have a null script_type I am closing this one. *** This bug has been marked as a duplicate of bug 5327 ***
Verified.