Bug 9873

Summary: patchtest-oe: in case LIC_FILES_CHKSUM changed, make sure commit message indicates the reason
Product: [Yocto Project Subprojects] Patchwork/Patchtest Reporter: Leonardo Sandoval Gonzalez <leonardo.sandoval.gonzalez>
Component: PatchtestAssignee: Jose Lamego <jose.a.lamego>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: Medium+ CC: bluelightning, richard.purdie
Version: 2.1   
Target Milestone: 2.2 M2   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Leonardo Sandoval Gonzalez 2016-07-04 16:32:52 UTC
The suite must at least check that subject contains the string 'lic_files_chksum'  or 'license' or 'checksum' in case the value of LIC_FILES_CHKSUM would change on behalf of the corresponding patch.
Comment 1 Paul Eggleton 2016-07-06 02:16:15 UTC
By "subject" you mean "commit message" here.
Comment 2 Leonardo Sandoval Gonzalez 2016-07-06 13:47:22 UTC
(In reply to comment #1)
> By "subject" you mean "commit message" here.

patchtest at the end is using mboxes (which contain code changes in the payload), so in patchtest context is indeed a subject.
Comment 3 Paul Eggleton 2016-07-06 20:05:42 UTC
The subject is the shortlog from the commit message, not the entire commit message. LIC_FILES_CHKSUM would typically be mentioned in the commit message but not the shortlog - hence in email terms it would not actually appear in the subject, just the message body.
Comment 4 Leonardo Sandoval Gonzalez 2016-07-06 20:30:30 UTC
(In reply to comment #3)
> The subject is the shortlog from the commit message, not the entire commit
> message. LIC_FILES_CHKSUM would typically be mentioned in the commit message
> but not the shortlog - hence in email terms it would not actually appear in
> the subject, just the message body.

I see. I was a misunderstood from my part. Thanks for clarifying this.