[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <65b155bf549e3_22a8cb294c7@willemb.c.googlers.com.notmuch>
Date: Wed, 24 Jan 2024 13:23:59 -0500
From: Willem de Bruijn <willemdebruijn.kernel@...il.com>
To: Jakub Kicinski <kuba@...nel.org>,
Willem de Bruijn <willemdebruijn.kernel@...il.com>
Cc: David Ahern <dsahern@...nel.org>,
Hangbin Liu <liuhangbin@...il.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"netdev-driver-reviewers@...r.kernel.org" <netdev-driver-reviewers@...r.kernel.org>,
pabeni@...hat.com
Subject: Re: [ANN] net-next is OPEN
Jakub Kicinski wrote:
> On Wed, 24 Jan 2024 12:42:46 -0500 Willem de Bruijn wrote:
> > > Here's a more handy link filtered down to failures (clicking on
> > > the test counts links here):
> > >
> > > https://netdev.bots.linux.dev/contest.html?branch=net-next-2024-01-24--15-00&executor=vmksft-net-mp&pass=0
> > >
> > > I have been attributing the udpg[rs]o and timestamp tests to you,
> > > but I haven't actually checked.. are they not yours? :)
> >
> > I just looked at the result file and assumed 0 meant fine. Oops.
>
> Sorry about the confusion there, make run_tests apparently always
> returns 0 and the result file holds the exit code :( It could be
> improved by I figured, as long as the JSON output is correct, investing
> the time in the web UI is probably a better choice than massaging
> the output files.
Absolutely. My bad for jumping to conclusions.
Powered by blists - more mailing lists