| Message ID | 20251219-mathieu-ptest-expect-fail-v1-1-d8f30c8b3e68@bootlin.com |
|---|---|
| State | New |
| Headers | show |
| Series | fragments/autobuilder: Add back PTEST_EXPECT_FAILURE | expand |
diff --git a/meta/conf/fragments/yocto-autobuilder/autobuilder.conf b/meta/conf/fragments/yocto-autobuilder/autobuilder.conf index 85987b08995a..a9ae99a451e6 100644 --- a/meta/conf/fragments/yocto-autobuilder/autobuilder.conf +++ b/meta/conf/fragments/yocto-autobuilder/autobuilder.conf @@ -10,4 +10,5 @@ SDK_EXT_TYPE = 'minimal' SDK_INCLUDE_TOOLCHAIN = '1' ESDK_LOCALCONF_REMOVE:append = 'BB_HASHSERVE' SDK_TOOLCHAIN_LANGS += 'go rust' +PTEST_EXPECT_FAILURE = '1'
The PTEST_EXPECT_FAILURE option setting was recently dropped from core-image-ptest [1]. This is probably the right thing to do, but we still want to use it on the autobuilder. Note, this will now be enabled on all images and not just the ptest ones, but this should not change the whole behaviour. [1] https://lists.openembedded.org/g/openembedded-core/message/227412 Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> --- meta/conf/fragments/yocto-autobuilder/autobuilder.conf | 1 + 1 file changed, 1 insertion(+) --- base-commit: 4bd920ad7d7279020ea6e561d0584ae70f33f751 change-id: 20251219-mathieu-ptest-expect-fail-a7b4fe3006f7 Best regards,