| Message ID | 20230727143627.3718496-3-alex@linutronix.de |
|---|---|
| State | Accepted, archived |
| Commit | 6f9db3f8de3dca9b0c87382561c70857d5b39e0f |
| Headers | show |
| Series | [01/21] meta: add missing summaries for image recipes | expand |
diff --git a/scripts/lib/devtool/standard.py b/scripts/lib/devtool/standard.py index 86ca77f7180..88a6ecd4219 100644 --- a/scripts/lib/devtool/standard.py +++ b/scripts/lib/devtool/standard.py @@ -567,6 +567,8 @@ def _extract_source(srctree, keep_temp, devbranch, sync, config, basepath, works logger.debug('writing append file %s' % appendfile) with open(appendfile, 'a') as f: f.write('###--- _extract_source\n') + f.write('deltask do_recipe_qa\n') + f.write('deltask do_recipe_qa_setscene\n') f.write('ERROR_QA:remove = "patch-fuzz"\n') f.write('DEVTOOL_TEMPDIR = "%s"\n' % tempdir) f.write('DEVTOOL_DEVBRANCH = "%s"\n' % devbranch)
The immediate reason is that the task is sstate enabled, and due to the way devtool sets up source extraction this causes bogus values to appear in tmp/sstate-control/index-* files. Also, recipe_qa may contain hard failures in the future, and it would be counterproductive for the failures to prevent devtool workflows (which may perhaps be about fixing the failure). An alternative would have been to not insert recipe_qa task before fetch task, but that would greatly delay the checks in larger bitbake builds, and it's better to run them as early as possible. Signed-off-by: Alexander Kanavin <alex@linutronix.de> --- scripts/lib/devtool/standard.py | 2 ++ 1 file changed, 2 insertions(+)