15531 2024-06-27 17:03:04 +0000 AUH: run core-image-ptest-${BPN} for testimage (not core-image-sato) 2026-04-21 14:56:18 +0000 1 1 6 Yocto Project Subprojects Automated Update Handler Automatic Update Handler 5.1 x86 Multiple NEW Medium+ enhancement 6.1 M1 1 tim.orling tim.orling randy.macleod apoorvsangal --- --- Yes (doc changes required) oldest_to_newest 99288 0 tim.orling 2024-06-27 17:03:04 +0000 Not sure that is is currently possible to expand variables in upgrade-helper.conf e.g. # If enabled, build and boots a test image, and runs integration tests on it # If upgraded packages have ptest support those are run as well # # Requires 'testimage' in INHERIT in your conf/local.conf and 'ptest' in your # distro's DISTRO_FEATURES. testimage=yes # This can be used to change the name of the test image. # testimage_name=core-image-ptest-${BPN} Probably the code behind testimage in AUH is not compatible with the concept anyway. But given the new capabilities with the mcextend/BBCLASSEXTEND "magic", it would make the testing of ptest-enabled updates much easier/more useful? 99289 1 alex.kanavin 2024-06-27 20:08:12 +0000 Here's the testimage code in AUH: https://git.yoctoproject.org/auto-upgrade-helper/tree/modules/testimage.py If I'm reading it right, it detects if the currently upgraded package has ptest enabled, and if so, adds ${PN}-ptest to the image. The image doesn't have to be sato, it can be something else, e.g. core-image-ptest or something even more minimal. Would that be sufficient? I'm not using this function, so I do not know how well that works. 99319 2 randy.macleod 2024-07-04 14:59:15 +0000 Put into needinfo by accident.