# running test ipv4 large
# Expected {65495 919 }, Total 2 packets
# Received {65495 919 }, Total 2 packets.
# Expected {64576 920 920 }, Total 3 packets
# Received {64576 ./gro: could not receive: Resource temporarily unavailable
# Expected {65495 919 }, Total 2 packets
# Received {65495 919 }, Total 2 packets.
# Expected {64576 920 920 }, Total 3 packets
# Received {64576 ./gro: could not receive: Resource temporarily unavailable
# Expected {65495 919 }, Total 2 packets
# Received {65495 919 }, Total 2 packets.
# Expected {64576 920 920 }, Total 3 packets
# Received {64576 ./gro: could not receive: Resource temporarily unavailable
....
# failed tests: ipv4_large. Please see log.txt for more logs
This is not a regression, I can see this failure in 5.15.0-28.29 as well. Open this one as the hint we're using indicates a different error message.
Issue found on 5.15.0-36.37 with P9 node baltar
# running test ipv4 large
# Expected {65495 919 }, Total 2 packets
# Received {65495 919 }, Total 2 packets.
# Expected {64576 920 920 }, Total 3 packets
# Received {64576 ./gro: could not receive: Resource temporarily unavailable
# Expected {65495 919 }, Total 2 packets
# Received {65495 919 }, Total 2 packets.
# Expected {64576 920 920 }, Total 3 packets
# Received {64576 ./gro: could not receive: Resource temporarily unavailable
# Expected {65495 919 }, Total 2 packets
# Received {65495 919 }, Total 2 packets.
# Expected {64576 920 920 }, Total 3 packets
# Received {64576 ./gro: could not receive: Resource temporarily unavailable
....
# failed tests: ipv4_large. Please see log.txt for more logs
This is not a regression, I can see this failure in 5.15.0-28.29 as well. Open this one as the hint we're using indicates a different error message.