4 failures reported in net:so_incoming_cpu on Jammy OEM 6.5
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-kernel-tests |
New
|
Undecided
|
Unassigned |
Bug Description
Issue found with J-oem-6.5.0-1005.5 and -1006 on bare-metal node wildcat.
This should not be considered as a regression since we were unable to test this kernel on bare-metals due to Intel lab outage.
The test result shows it's a bit flaky.
Test failed with 4 sub-tests (1, 4, 9, 12) on -1005:
# # RUN so_incoming_
# # so_incoming_
# # test1: Test terminated by assertion
# # FAIL so_incoming_
# not ok 1 so_incoming_
# # RUN so_incoming_
# # so_incoming_
# # test1: Test terminated by assertion
# # FAIL so_incoming_
# not ok 4 so_incoming_
# # RUN so_incoming_
# # so_incoming_
# # test3: Test terminated by assertion
# # FAIL so_incoming_
# not ok 9 so_incoming_
# # RUN so_incoming_
# # so_incoming_
# # test3: Test terminated by assertion
# # FAIL so_incoming_
# not ok 12 so_incoming_
Test failed with 4 sub-tests (3, 4, 8, 12) on -1006:
# # RUN so_incoming_
# # so_incoming_
# # test3: Test terminated by assertion
# # FAIL so_incoming_
# not ok 3 so_incoming_
# # RUN so_incoming_
# # so_incoming_
# # test1: Test terminated by assertion
# # FAIL so_incoming_
# not ok 4 so_incoming_
# # RUN so_incoming_
# # so_incoming_
# # test2: Test terminated by assertion
# # FAIL so_incoming_
# not ok 8 so_incoming_
# # RUN so_incoming_
# # so_incoming_
# # test3: Test terminated by assertion
# # FAIL so_incoming_
# not ok 12 so_incoming_