dtb-fit-image: fix do_generate_qcom_fitimage[vardeps]#1638
dtb-fit-image: fix do_generate_qcom_fitimage[vardeps]#1638ricardosalveti merged 1 commit intoqualcomm-linux:masterfrom
Conversation
|
More context in #1618 (comment) |
|
@quaresmajose please clean up your git commit message, no need to dump the variables, also please break lines to the 80 columns max. |
|
When I proposed #1618 it didn't work when testing locally, but I extended one variable locally again (not removing it, as that would cause cache to be invalidated) and it worked correctly, so fine with the change. |
Test run workflowTest jobs for commit 90d45d2
All jobs summary
|
Test Results 47 files + 16 106 suites +75 3h 35m 31s ⏱️ + 2h 12m 39s For more details on these failures, see this check. Results for commit e2b721b. ± Comparison against base commit 0362862. ♻️ This comment has been updated with latest results. |
2b272aa add the FIT_DTB_COMPATIBLE in task signature parsing all the keys and values of the variable. But we can use the FIT_DTB_COMPATIBLE directly on the vardeps of the qcom_generate_qcom_fitimage task. This was tested building linux-qcom-next and afer that removing one element from FIT_DTB_COMPATIBLE[...] = ...' then looking at the signatures and the change is caught by bitbake. | Task linux-qcom-next:do_generate_qcom_fitimage couldn't be used from the cache because: | ... | changed items: frozenset({'FIT_DTB_COMPATIBLE[talos-evk+talos-evk-lvds-auo_g133han01]'}) | Dependency on Variable FIT_DTB_COMPATIBLE[talos-evk+talos-evk-lvds-auo_g133han01] was removed Signed-off-by: Jose Quaresma <jose.quaresma@oss.qualcomm.com>
90d45d2 to
e2b721b
Compare
Also check when we don't remove the element:
--- a/conf/machine/include/fit-dtb-compatible.inc
+++ b/conf/machine/include/fit-dtb-compatible.inc
@@ -109,4 +109,4 @@ FIT_DTB_COMPATIBLE[sm8450-hdk] = "qcom,sm8450-hdk"
FIT_DTB_COMPATIBLE[sm8750-mtp] = "qcom,sm8750-mtp"
FIT_DTB_COMPATIBLE[talos-evk+talos-evk-camera-imx577] = "qcom,qcs615v1.1-iot"
FIT_DTB_COMPATIBLE[talos-evk+talos-evk-camx] = "qcom,qcs615v1.1-iot-camx"
-FIT_DTB_COMPATIBLE[talos-evk+talos-evk-lvds-auo_g133han01] = "qcom,talos-evk-lvds-auo,g133han01"
+FIT_DTB_COMPATIBLE[talos-evk+talos-evk-lvds-auo_g133han01-] = "qcom,talos-evk-lvds-auo,g133han01"and the signature
--- a/conf/machine/include/fit-dtb-compatible.inc
+++ b/conf/machine/include/fit-dtb-compatible.inc
@@ -109,4 +109,4 @@ FIT_DTB_COMPATIBLE[sm8450-hdk] = "qcom,sm8450-hdk"
FIT_DTB_COMPATIBLE[sm8750-mtp] = "qcom,sm8750-mtp"
FIT_DTB_COMPATIBLE[talos-evk+talos-evk-camera-imx577] = "qcom,qcs615v1.1-iot"
FIT_DTB_COMPATIBLE[talos-evk+talos-evk-camx] = "qcom,qcs615v1.1-iot-camx"
-FIT_DTB_COMPATIBLE[talos-evk+talos-evk-lvds-auo_g133han01] = "qcom,talos-evk-lvds-auo,g133han01"
+FIT_DTB_COMPATIBLE[talos-evk+talos-evk-lvds-auo_g133han01] = "qcom,talos-evk-lvds-auo,g133han01-"
and the signature |
Test run workflowTest jobs for commit e2b721b
All jobs summary
|
Test run workflowTest jobs for commit e2b721b
All jobs summary
|
c93093b
into
qualcomm-linux:master
2b272aa add the FIT_DTB_COMPATIBLE in task signature parsing all the keys
and values of the variable. But we can use the FIT_DTB_COMPATIBLE directly
on the vardeps of the qcom_generate_qcom_fitimage task.
This was tested building linux-qcom-next and afer that
removing one element from FIT_DTB_COMPATIBLE[...] = ...'
then looking at the signatures and the change is caught by bitbake.
| Task linux-qcom-next:do_generate_qcom_fitimage couldn't be used from the cache because:
| ...
| changed items: frozenset({'FIT_DTB_COMPATIBLE[talos-evk+talos-evk-lvds-auo_g133han01]'})
| Dependency on Variable FIT_DTB_COMPATIBLE[talos-evk+talos-evk-lvds-auo_g133han01] was removed