canonical-ubuntu-qa team mailing list archive
-
canonical-ubuntu-qa team
-
Mailing list archive
-
Message #03165
[Bug 2006692] Re: net:fcnal-test.sh didn't return a non-zero value even with some sub-tests failed
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/2006692
Title:
net:fcnal-test.sh didn't return a non-zero value even with some sub-
tests failed
Status in ubuntu-kernel-tests:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Bug description:
[Impact]
The net/fcnal-test.sh on F/J won't return a non-zero value even with
some sub test cases failed, here is an example on Jammy:
# Tests passed: 857
# Tests failed: 5
ok 1 selftests: net: fcnal-test.sh
Therefore it's marked as PASSED on our report and making it difficult
to spot these failures:
# With VRF
# SYSCTL: net.ipv4.raw_l3mdev_accept=1
# TEST: ping local, VRF bind - VRF IP [FAIL]
# TEST: ping local, device bind - ns-A IP [FAIL]
# SYSCTL: net.ipv4.ping_group_range=0 2147483647
# SYSCTL: net.ipv4.raw_l3mdev_accept=1
# TEST: ping local, VRF bind - VRF IP [FAIL]
# TEST: ping local, device bind - ns-A IP [FAIL]
# With VRF
# SYSCTL: net.ipv4.raw_l3mdev_accept=1
# SYSCTL: net.ipv4.ping_group_range=0 2147483647
# SYSCTL: net.ipv4.raw_l3mdev_accept=1
# TEST: ping out, vrf device+address bind - ns-B IPv6 LLA [FAIL]
[Fix]
* 0f8a3b48f9 selftests: net/fcnal-test.sh: add exit code
This patch can be cherry-picked into Focal and Jammy kernel.
We don't have this test in Bionic, and this patch has already landed
on Kinetic and OEM-5.17
[Test]
Run the patched test, the return value will be 1 whenever the number
of failed test cases is not 0.
[Where problems could occur]
Change limited to testing tools, but we're expected to see new failures
in Jammy. With bug 2006391 fixed later on, we will see failures
reported in F/K as well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2006692/+subscriptions