Re: net-next/master bisection: boot on beaglebone-black

Re: net-next/master bisection: boot on beaglebone-black

[David Miller]

From: "kernelci.org bot" <bot@kernelci.org>
Date: Fri, 22 Nov 2019 04:16:01 -0800 (PST)

>     mdio_bus: Fix PTR_ERR applied after initialization to constant
>     
>     Fix coccinelle warning:
>     
>     ./drivers/net/phy/mdio_bus.c:67:5-12: ERROR: PTR_ERR applied after initialization to constant on line 62
>     ./drivers/net/phy/mdio_bus.c:68:5-12: ERROR: PTR_ERR applied after initialization to constant on line 62

The kernelci.org bot has posted at least a half dozen of these bisection
results for the same exact bug, which we've fixed two days ago....

This is becomming more like spam and not very useful....

Re: net-next/master bisection: boot on beaglebone-black

[Guillaume Tucker]

On 22/11/2019 17:36, David Miller wrote:
> From: "kernelci.org bot" <bot@kernelci.org>
> Date: Fri, 22 Nov 2019 04:16:01 -0800 (PST)
> 
>>     mdio_bus: Fix PTR_ERR applied after initialization to constant
>>     
>>     Fix coccinelle warning:
>>     
>>     ./drivers/net/phy/mdio_bus.c:67:5-12: ERROR: PTR_ERR applied after initialization to constant on line 62
>>     ./drivers/net/phy/mdio_bus.c:68:5-12: ERROR: PTR_ERR applied after initialization to constant on line 62
> 
> The kernelci.org bot has posted at least a half dozen of these bisection
> results for the same exact bug, which we've fixed two days ago....
> 
> This is becomming more like spam and not very useful....

As far as I can tell, it's the first time someone replies to say
this issue is already fixed.  Sorry if I've missed an email.

Also, it's apparently not fixed in the net-next tree which
explains why it was reported again.  I guess we need to disable
bisections in net-next until it gets rebased and includes the
fix, and add a way to mark issues fixed somewhere else in
KernelCI to avoid this situation in the future.

Thanks,
Guillaume

Re: net-next/master bisection: boot on beaglebone-black

[David Miller]

From: Guillaume Tucker <guillaume.tucker@collabora.com>
Date: Fri, 22 Nov 2019 18:02:06 +0000

> As far as I can tell, it's the first time someone replies to say
> this issue is already fixed.  Sorry if I've missed an email.

I saw the first one and just ignored it hoping that since I had
the fix in 'net' these emails would simply stop.

> Also, it's apparently not fixed in the net-next tree which
> explains why it was reported again.  I guess we need to disable
> bisections in net-next until it gets rebased and includes the
> fix, and add a way to mark issues fixed somewhere else in
> KernelCI to avoid this situation in the future.

If you're not combining the net and the net-next tree, as Stephen
Rothwell's tree is doing, then you're going to run into this problem
every single day and spam us with these messages.

What is being done right now doesn't work.  You can't just wait for
net integration into net-next, that doesn't cut it.

Re: net-next/master bisection: boot on beaglebone-black

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 808 bytes --]

On Fri, Nov 22, 2019 at 10:11:47AM -0800, David Miller wrote:

> If you're not combining the net and the net-next tree, as Stephen
> Rothwell's tree is doing, then you're going to run into this problem
> every single day and spam us with these messages.

> What is being done right now doesn't work.  You can't just wait for
> net integration into net-next, that doesn't cut it.

Is there a writeup somewhere of how your trees are expected to work?
That might help testing people figure things out, what you're doing is a
bit unusual and people working on testing infrastructure are likely not
going to be as engaged with the process for specific trees as developers
are.  I didn't spot anything in Docmentation/ and the wiki link in
MAINTAINERS seems broken but I might've been looking in the wrong places.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]