On Wed, 16 Apr 2025 11:00:35 -0300 Victor Nogueira wrote:
> On 4/16/25 10:52, Jakub Kicinski wrote:
> > On Tue, 15 Apr 2025 14:43:14 +0200 [email protected]
> > wrote:  
> >> From: Chia-Yu Chang <[email protected]>
> >>
> >> Update configuration of tc-tests and preload DualPI2 module for self-tests,
> >> and add folloiwng self-test cases for DualPI2:
> >>
> >>    Test a4c7: Create DualPI2 with default setting
> >>    Test 2130: Create DualPI2 with typical_rtt and max_rtt
> >>    Test 90c1: Create DualPI2 with max_rtt
> >>    Test 7b3c: Create DualPI2 with any_ect option
> >>    Test 49a3: Create DualPI2 with overflow option
> >>    Test d0a1: Create DualPI2 with drop_enqueue option
> >>    Test f051: Create DualPI2 with no_split_gso option  
> > 
> > it appears applying this causes the tdc test runner to break,
> > could you take a look?
> > 
> > https://github.com/p4tc-dev/tc-executor/blob/storage/artifacts/79725/1-tdc-sh/stdout
> >   
> 
> It seems like the breakage happens because the iproute2 patch
> is not in yet. I applied the iproute2 patch locally and the
> tests succeeded. The next iteration should run with it applied
> so the breakage should stop.

Thank you! returned the patches to the queue, 
the net-next-2025-04-17--00-00 branch should have them again.


Reply via email to