canonical-ubuntu-qa team mailing list archive

[Po-Hsu Lin <2071861@xxxxxxxxxxxxxxxxxx>]

This issue can be found on N-oem-6.8.0-1008.8, KUAN-YING has confirmed
that this commit 1a4ea83a that introduced the test case change was
landed on N-oem-6.8 since -1008.

As it's limiting first 100 output, we might need to do some manual test
to see if 100 is enough to generate 3 different events for this test to
catch.

** Tags added: 6.8 noble sru-20240610

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