canonical-ubuntu-qa team mailing list archive

[Magali Lemes do Sacramento <2071861@xxxxxxxxxxxxxxxxxx>]

Seems like it is an issue with the test and not with the kernels, as both these kernels derive from j:linux version 5.15.0-115.125, which changed the test[1] a bit.
Quickly tested that reverting that commit makes the test pass again on m5a.large.
The commit states that "100 lines of output would be enough to judge whether there are more than 3 types of sched events", but it seems like that is not the case for some instances.

[1]: https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/jammy/commit/?h=Ubuntu-5.15.0-115.125&id=dcb06c117506b324c5adf27235e34f235b9171de

-- 
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/2071861

Title:
  ftrace:test.d--event--subsystem-enable.tc fails on some instances

Status in ubuntu-kernel-tests:
  New

Bug description:
  In the 2024.06.10 SRU cycle, the ftrace:test.d--event--subsystem-
  enable.tc testcases from ubuntu_kselftests_ftrace are failing:

  === Ftrace unit tests ===
  [1] event tracing - enable/disable with subsystem level files   [FAIL]
  [2] (instance)  event tracing - enable/disable with subsystem level files       [FAIL]

  
  # of passed:  0
  # of failed:  2
  # of unresolved:  0
  # of untested:  0
  # of unsupported:  0
  # of xfailed:  0
  # of undefined(test bug):  0

  The relevant part from the verbose output is `fail at least fork, exec
  and exit events should be recorded`

  This was found on these kernels:
  - j:aws-fips version 5.15.0-1065.71+fips1 on the m5a.large instance.
  - j:gcp-fips version 5.15.0-1064.72+fips1 on the n2d-standard-2 instance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2071861/+subscriptions