Paolo Abeni wrote:
The gro self-tests sends the packets to be aggregated with multiple write operations.
When running is slow environment, it's hard to guarantee that the GRO engine will wait for the last packet in an intended train.
The above causes almost deterministic failures in our CI for the 'large' test-case.
Address the issue explicitly ignoring failures for such case in slow environments (KSFT_MACHINE_SLOW==true).
Fixes: 7d1575014a63 ("selftests/net: GRO coalesce test") Signed-off-by: Paolo Abeni pabeni@redhat.com
Reviewed-by: Willem de Bruijn willemb@google.com