Hints removed. Closing this bug.
This issue cannot be found on J-azure, J-azure-fips, J-gcp-fips, J-mtk,
J-nvidia-tegra, J-xilinx.
We don't run this test on J-raspi, J-bluefield.
** Changed in: ubuntu-kernel-tests
Status: In Progress => Fix Released
** Tags removed: verification-needed-jammy-linux-azure
verification-needed-jammy-linux-azure-fips
verification-needed-jammy-linux-bluefield
verification-needed-jammy-linux-gcp-fips verification-needed-jammy-linux-mtk
verification-needed-jammy-linux-nvidia-tegra
verification-needed-jammy-linux-raspi
verification-needed-jammy-linux-xilinx-zynqmp
** Tags added: verification-done-jammy-linux-azure
verification-done-jammy-linux-azure-fips
verification-done-jammy-linux-bluefield verification-done-jammy-linux-gcp-fips
verification-done-jammy-linux-mtk verification-done-jammy-linux-nvidia-tegra
verification-done-jammy-linux-raspi verification-done-jammy-linux-xilinx-zynqmp
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2029405
Title:
Change in trace file leads to test timeout in ftrace tests on 5.15
ARM64
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2029405/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
