Subject: Re: [TEST] forwarding/router_bridge_lag.sh started to flake on Monday

From: Jakub Kicinski <[email-masked]>
Date: Sat, 24 Aug 2024 14:27:21 -0700

On Fri, 23 Aug 2024 18:13:01 +0200 Petr Machata wrote:
> >> +	ip link set dev $swp2 down
> >> +	ip link set dev $swp1 down
> >> +
> >>  	h2_destroy
> >>  	h1_destroy
> >>    
> >
> > no_forwarding always runs in thread 0 because it's the slowest tests
> > and we try to run from the slowest as a basic bin packing heuristic.
> > Clicking thru the failures I don't see them on thread 0.  
> 
> Is there a way to see what ran before?

The data is with the outputs in the "info" file, not in the DB :(
I hacked up a bash script to fetch those:
https://github.com/linux-netdev/nipa/blob/main/contest/cithreadmap

Looks like for the failed cases local_termination.sh always runs 
before router-bridge, and whatever runs next flakes:

Thread4-VM0
	 5-local-termination-sh/
	 20-router-bridge-lag-sh/
	 20-router-bridge-lag-sh-retry/

Thread4-VM0
	 5-local-termination-sh/
	 16-router-bridge-1d-lag-sh/
	 16-router-bridge-1d-lag-sh-retry/