15631 2024-10-23 16:37:34 +0000 Patchtest branch handling causes issues in master-next 2025-02-13 16:05:11 +0000 1 1 6 Yocto Project Subprojects Patchwork/Patchtest Patchtest 5.2 x86 Multiple RESOLVED FIXED Medium+ normal 5.2 M2 1 tgamblin tgamblin randy.macleod yoann.congal --- --- No (bug/feature does not impact docs) oldest_to_newest 99977 0 tgamblin 2024-10-23 16:37:34 +0000 See: https://valkyrie.yoctoproject.org/#/builders/71/builds/292/steps/12/logs/stdio and the corresponding patch in master-next: https://git.openembedded.org/openembedded-core/commit/?h=master-next&id=81c2c4700be3f3291dc44636f78d5b46d01c2153 Patchtest works by identifying the current branch and checking out a new test branch based on the current PID to test patches. However, this isn't working correctly when e.g. testing new selftests on the AB. This is probably due to the code resetting to the master branch, rather than whatever branch it began with (i.e. master-next), when testing for a single patch is complete. 100940 1 tgamblin 2025-02-13 16:05:11 +0000 Should be fixed by: https://git.yoctoproject.org/poky/commit/?id=4ed3c83240b3a761af71a3d10e295b4e5e356f00