| Message ID | 592c889bc58a0d2b99ce4669d927fc59886b760a.1772220652.git.tim.orling@konsulko.com |
|---|---|
| State | New |
| Headers | show |
| Series | Introduce PTEST_RUNNER_TIMEOUT variable | expand |
diff --git a/meta/classes-recipe/testimage.bbclass b/meta/classes-recipe/testimage.bbclass index 7a48ed6bfe3..9902b8a5682 100644 --- a/meta/classes-recipe/testimage.bbclass +++ b/meta/classes-recipe/testimage.bbclass @@ -112,7 +112,9 @@ TESTIMAGELOCK:qemuall = "" TESTIMAGE_DUMP_DIR ?= "${LOG_DIR}/runtime-hostdump/" -TESTIMAGE_UPDATE_VARS ?= "DL_DIR WORKDIR DEPLOY_DIR_IMAGE IMAGE_LINK_NAME IMAGE_NAME" +TESTIMAGE_UPDATE_VARS ?= "DL_DIR WORKDIR DEPLOY_DIR_IMAGE IMAGE_LINK_NAME IMAGE_NAME PTEST_RUNNER_TIMEOUT" + +PTEST_RUNNER_TIMEOUT ?= "450" testimage_dump_monitor () { query-status
QB_MEM works in recipe scope because testimage.bbclass reads it from the current recipe datastore (d) at test time via the qemuboot.conf mechanism. PTEST_RUNNER_TIMEOUT was only available through testdata.json (written during image build via export2json). The testimage task reads td from the potentially stale testdata.json, and PTEST_RUNNER_TIMEOUT was never refreshed from the live recipe context. [YOCTO #16163] Signed-off-by: Tim Orling <tim.orling@konsulko.com> --- meta/classes-recipe/testimage.bbclass | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)