Bug 10738 - patchtest: Patches not sent as reply to their respective series/root message should trigger a warning message
Summary: patchtest: Patches not sent as reply to their respective series/root message ...
Status: RESOLVED INVALID
Alias: None
Product: Patchwork/Patchtest
Classification: Yocto Project Subprojects
Component: Patchtest Testsuite (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 2.5
Assignee: Leonardo Sandoval Gonzalez
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-11-28 18:11 UTC by Jose Lamego
Modified: 2017-12-06 17:18 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 Jose Lamego 2016-11-28 18:11:42 UTC 
Patchtest should have a test to detect patches that may belong to a series (due to the "x/n" prefix in subject), but that were not sent as a reply to any root message. This should not cause the test to fail, but to trigger a warning.

An example of such a patch email is in 
http://lists.openembedded.org/pipermail/openembedded-core/2016-November/129348.html
Comment 1 Leonardo Sandoval Gonzalez 2017-06-15 19:39:50 UTC 
(In reply to comment #0)
> Patchtest should have a test to detect patches that may belong to a series
> (due to the "x/n" prefix in subject), but that were not sent as a reply to
> any root message. This should not cause the test to fail, but to trigger a
> warning.
> 
> An example of such a patch email is in 
> http://lists.openembedded.org/pipermail/openembedded-core/2016-November/
> 129348.html

Not sure if we way to trigger a warning/fail on this case. People usually send their n revision without indicating the in-reply-to message-id of the n-1 revision.

Also, for the moment, patchtest just trigger failures, not warnings, but at the end if patchwork is sending a email to the mailing list on behalf of patchtest, we want actions to be done from the developer, so I am not sure if failures/warnings would make sense.

Paul, thoughts about it?
Comment 2 Leonardo Sandoval Gonzalez 2017-07-07 17:01:20 UTC 
comment 1 basically resumes the decision to mark it as invalid.
Comment 3 Leonardo Sandoval Gonzalez 2017-07-07 17:07:26 UTC 
(In reply to comment #2)
> comment 1 basically resumes the decision to mark it as invalid.

s/resumes/summarizes