Bug 15631 - Patchtest branch handling causes issues in master-next
Summary: Patchtest branch handling causes issues in master-next
Status: RESOLVED FIXED
Alias: None
Product: Patchwork/Patchtest
Classification: Yocto Project Subprojects
Component: Patchtest (show other bugs)
Version: 5.2
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 5.2 M2
Assignee: Trevor Gamblin
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2024-10-23 16:37 UTC by Trevor Gamblin
Modified: 2025-02-13 16:05 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Trevor Gamblin 2024-10-23 16:37:34 UTC 
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.