Bug 15258 - Patchtest should test an entire series together, rather than checking patches individually
Summary: Patchtest should test an entire series together, rather than checking patches...
Status: IN PROGRESS DESIGN
Alias: None
Product: Patchwork/Patchtest
Classification: Yocto Project Subprojects
Component: Patchtest (show other bugs)
Version: 5.0
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 6.1
Assignee: Trevor Gamblin
QA Contact:
URL:
Whiteboard:
: 15240 (view as bug list)
Depends on:
Blocks:
 
Reported: 2023-10-27 11:39 UTC by Trevor Gamblin
Modified: 2026-02-26 16:05 UTC (History)
1 user (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)

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 2023-10-27 11:39:08 UTC 
The patchtest tooling (i.e. patchtest itself, patchtest-get-series, and the core-image-patchtest image) all operate under the assumption that a patch series will be split before testing. This change has allowed the suite to become usable again, but it does not provide as complete of an assessment as it could, and makes testing mergeability difficult. Improve the patchtest code so that it properly handles an entire series.
Comment 1 Trevor Gamblin 2024-02-11 17:51:42 UTC 
*** Bug 15240 has been marked as a duplicate of this bug. ***
Comment 2 Trevor Gamblin 2024-02-11 17:53:25 UTC 
From 15240 - an improvement would be to add a --test-merge flag (or similar) that needs to be provided for that test to run. This way, one or more patches can be tested for other issues (e.g. missing CVE tags and general formatting) without worrying about merge status. It would also help with improving patchtest's modularity with respect to layers other than oe-core.