[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240124085919.316a48f9@kernel.org>
Date: Wed, 24 Jan 2024 08:59:19 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: David Ahern <dsahern@...nel.org>
Cc: Paolo Abeni <pabeni@...hat.com>, 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>
Subject: Re: [ANN] net-next is OPEN
On Wed, 24 Jan 2024 09:35:09 -0700 David Ahern wrote:
> > This is the latest run:
> >
> > https://netdev-2.bots.linux.dev/vmksft-net-mp/results/435141/1-fcnal-test-sh/stdout
> >
> > the nettest warning is indeed gone, but the failures are the same:
>
> yep, I will send a formal patch. I see the timeout is high enough, so
> good there.
Well, kinda, to be honest I did bump the time to 4000s locally.
The runtime of the entire net suite 1h 10min - that's pretty much
the runtime of this one test :) The VMs run the tests without
HW virtualization, so they are a bit slower, but it'd be nice
if no local hacks were necessary.
I haven't sent a patch to bump it because it may make more sense
to split the test into multiple. But as a stop gap we can as well
bump the timeout.
> > $ grep FAIL stdout
> > # TEST: ping local, VRF bind - VRF IP [FAIL]
> > # TEST: ping local, device bind - ns-A IP [FAIL]
> > # TEST: ping local, VRF bind - VRF IP [FAIL]
> > # TEST: ping local, device bind - ns-A IP [FAIL]
> >
> > :(
>
> known problems. I can disable the tests for now so we avoid regressions,
> and add to the TO-DO list for someone with time.
Sounds good!
Powered by blists - more mailing lists