Re: The robot is broken (was: Re: [PATCH 1/3] USB: serial: return errors from break handling)

[Philip Li]

On Sun, Jun 04, 2023 at 02:41:27PM +0200, Johan Hovold wrote:
> On Sat, Jun 03, 2023 at 10:40:42AM +0800, kernel test robot wrote:
> > BCC: lkp@xxxxxxxxx
> > CC: oe-kbuild-all@xxxxxxxxxxxxxxx
> > In-Reply-To: <20230602124642.19076-2-johan@xxxxxxxxxx>
> > References: <20230602124642.19076-2-johan@xxxxxxxxxx>
> > TO: Johan Hovold <johan@xxxxxxxxxx>
> > TO: Johan Hovold <johan@xxxxxxxxxx>
> > CC: "Greg Kroah-Hartman" <gregkh@xxxxxxxxxxxxxxxxxxx>
> > CC: linux-usb@xxxxxxxxxxxxxxx
> > CC: linux-kernel@xxxxxxxxxxxxxxx
> > CC: Corey Minyard <minyard@xxxxxxx>
> > 
> > Hi Johan,
> > 
> > kernel test robot noticed the following build warnings:
> 
> > New smatch warnings:
> > drivers/usb/serial/io_edgeport.c:1601 edge_break() error: uninitialized symbol 'status'.
> 
> Thanks for the report. Now fixed up in v2:
> 
> 	https://lore.kernel.org/lkml/20230604123505.4661-1-johan@xxxxxxxxxx
> 
> The robot currently appears to be broken though as this report was never
> sent to me or the relevant mailing lists (and I just happened to see it
> by chance).

Thanks a lot Johan for checking this. For now, the bot has 2 similar mailing lists,
one is oe-kbuild-all@xxxxxxxxxxxxxxx, which contains the high confidence report that
is sent directly to author and related CC. Another one is this oe-kbuild@xxxxxxxxxxxxxxx,
that we will send low confidence issues here and they will only be really reported
out after manual check. So we can reduce false positives.

But sometimes, we may miss some reports of real issues, sorry about this.

> 
> Looks like there's a stray newline in the output of your scripts which
> causes the mail headers above to be included in the body instead.

Thanks, yes, this is by design, when the report is confirmed, it helps to send
out the report to actual users by removing this extra line.

> 
> Johan
>