diff mbox series

[V3,2/2] core-image-ptest: drop PTEST_EXPECT_FAILURE

Message ID 20251209020039.2341108-2-Qi.Chen@windriver.com
State New
Headers show
Series [V3,1/2] oeqa/runtime/cases/ptest.py: use to_boolean for PTEST_EXPECT_FAILURE | expand

Commit Message

Chen, Qi Dec. 9, 2025, 2 a.m. UTC 
From: Chen Qi <Qi.Chen@windriver.com>

This variable setting is not helping people now. Because in practice,
ptest failure warnings on autobuilder are still catched and reported
back to developer.

In addition, setting this value to 1 is sometimes causing confusion for
developers.

As an example, I used 'bitbake core-image-ptest-util-linux:do_testimage'.
It succeeded with warning message. I didn't notice the warning message.
I saw the command succeeded and I tought util-linux ptest is OK. But
in actual fact, the ptest failed. It's the PTEST_EXPECT_FAILURE setting
in this core-image-ptest.bb that is not giving me error.

In summary, a simple erroring out action should be clearer.

Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
---
 meta/recipes-core/images/core-image-ptest.bb | 3 ---
 1 file changed, 3 deletions(-)
diff mbox series

Patch

diff --git a/meta/recipes-core/images/core-image-ptest.bb b/meta/recipes-core/images/core-image-ptest.bb
index 017f05f81b..0b1eeb1a58 100644
--- a/meta/recipes-core/images/core-image-ptest.bb
+++ b/meta/recipes-core/images/core-image-ptest.bb
@@ -41,9 +41,6 @@  QB_MEM:virtclass-mcextend-tcl = "-m 5100"
 
 TEST_SUITES = "ping ssh parselogs ptest"
 
-# Sadly at the moment the full set of ptests is not robust enough and sporadically fails in random places
-PTEST_EXPECT_FAILURE = "1"
-
 python () {
     if not d.getVar("MCNAME"):
         raise bb.parse.SkipRecipe("No class extension set")