Public bug reported:

Failing on Jammy IBM 5.15.0-1033.36 on janbi AMD instance.
host: janbi. Is passing on other hosts (eg. kili Intel machine)

17:39:47 DEBUG| Persistent state client.unexpected_reboot now set to 
('ubuntu_kernel_selftests.ftrace:ftracetest', 
'ubuntu_kernel_selftests.ftrace:ftracetest')
17:39:47 DEBUG| Waiting for pid 1052404 for 9000 seconds
17:39:47 WARNI| System python is too old, crash handling disabled
17:39:47 DEBUG| Running 'make run_tests -C ftrace TEST_PROGS=ftracetest 
TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
17:39:47 DEBUG| [stdout] make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
17:39:47 DEBUG| [stdout] TAP version 13
17:39:47 DEBUG| [stdout] 1..1
17:39:47 DEBUG| [stdout] # selftests: ftrace: ftracetest
17:39:48 DEBUG| [stdout] # === Ftrace unit tests ===
17:39:48 DEBUG| [stdout] # [1] Basic trace file check   [PASS]
17:43:45 DEBUG| [stdout] # [2] Basic test for tracers   [PASS]
17:43:47 DEBUG| [stdout] # [3] Basic trace clock test   [PASS]
17:43:47 DEBUG| [stdout] # [4] Basic event tracing check        [PASS]
17:43:48 DEBUG| [stdout] # [5] Change the ringbuffer size       [PASS]
17:44:03 DEBUG| [stdout] # [6] Snapshot and tracing setting     [PASS]
17:44:04 DEBUG| [stdout] # [7] trace_pipe and trace_marker      [PASS]
18:15:52 DEBUG| [stdout] # [8] Test ftrace direct functions against tracers     
[PASS]
18:16:13 DEBUG| [stdout] # [9] Test ftrace direct functions against kprobes     
[PASS]
18:16:13 DEBUG| [stdout] # [10] Generic dynamic event - add/remove eprobe 
events        [PASS]
18:16:14 DEBUG| [stdout] # [11] Generic dynamic event - add/remove kprobe 
events        [PASS]
18:16:14 DEBUG| [stdout] # [12] Generic dynamic event - add/remove synthetic 
events     [PASS]
18:16:14 DEBUG| [stdout] # [13] Generic dynamic event - selective clear 
(compatibility) [PASS]
18:16:15 DEBUG| [stdout] # [14] Generic dynamic event - generic clear event     
[PASS]
18:16:15 DEBUG| [stdout] # [15] Generic dynamic event - check if duplicate 
events are caught    [PASS]
18:16:16 DEBUG| [stdout] # [16] event tracing - enable/disable with event level 
files   [PASS]
18:16:17 DEBUG| [stdout] # [17] event tracing - restricts events based on pid 
notrace filtering [PASS]
18:16:18 DEBUG| [stdout] # [18] event tracing - restricts events based on pid   
[PASS]
TEST SYSTEM FAILURE DETECTED Test results file 
'/home/maas/workspace/jammy-linux-ibm-ibm-amd64-5.15.0-1033.36-s2-janbi-ubuntu_kernel_selftests/kernel-results.xml'
 not found.


Console log also attached

** Affects: ubuntu-kernel-tests
     Importance: Undecided
         Status: New


** Tags: sru-20230515 ubuntu-kernel-selftests

** Attachment added: "Jammy IBM 5.15.0-1033.36 ftracetest console log"
   
https://bugs.launchpad.net/bugs/2025174/+attachment/5682368/+files/ubuntu_kernel_selftests-console.log

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

Title:
  ftracetest ACPI BIOS Error on jammy-ibm on janbi instance

Status in ubuntu-kernel-tests:
  New

Bug description:
  Failing on Jammy IBM 5.15.0-1033.36 on janbi AMD instance.
  host: janbi. Is passing on other hosts (eg. kili Intel machine)

  17:39:47 DEBUG| Persistent state client.unexpected_reboot now set to 
('ubuntu_kernel_selftests.ftrace:ftracetest', 
'ubuntu_kernel_selftests.ftrace:ftracetest')
  17:39:47 DEBUG| Waiting for pid 1052404 for 9000 seconds
  17:39:47 WARNI| System python is too old, crash handling disabled
  17:39:47 DEBUG| Running 'make run_tests -C ftrace TEST_PROGS=ftracetest 
TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
  17:39:47 DEBUG| [stdout] make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
  17:39:47 DEBUG| [stdout] TAP version 13
  17:39:47 DEBUG| [stdout] 1..1
  17:39:47 DEBUG| [stdout] # selftests: ftrace: ftracetest
  17:39:48 DEBUG| [stdout] # === Ftrace unit tests ===
  17:39:48 DEBUG| [stdout] # [1] Basic trace file check [PASS]
  17:43:45 DEBUG| [stdout] # [2] Basic test for tracers [PASS]
  17:43:47 DEBUG| [stdout] # [3] Basic trace clock test [PASS]
  17:43:47 DEBUG| [stdout] # [4] Basic event tracing check      [PASS]
  17:43:48 DEBUG| [stdout] # [5] Change the ringbuffer size     [PASS]
  17:44:03 DEBUG| [stdout] # [6] Snapshot and tracing setting   [PASS]
  17:44:04 DEBUG| [stdout] # [7] trace_pipe and trace_marker    [PASS]
  18:15:52 DEBUG| [stdout] # [8] Test ftrace direct functions against tracers   
[PASS]
  18:16:13 DEBUG| [stdout] # [9] Test ftrace direct functions against kprobes   
[PASS]
  18:16:13 DEBUG| [stdout] # [10] Generic dynamic event - add/remove eprobe 
events      [PASS]
  18:16:14 DEBUG| [stdout] # [11] Generic dynamic event - add/remove kprobe 
events      [PASS]
  18:16:14 DEBUG| [stdout] # [12] Generic dynamic event - add/remove synthetic 
events   [PASS]
  18:16:14 DEBUG| [stdout] # [13] Generic dynamic event - selective clear 
(compatibility)       [PASS]
  18:16:15 DEBUG| [stdout] # [14] Generic dynamic event - generic clear event   
[PASS]
  18:16:15 DEBUG| [stdout] # [15] Generic dynamic event - check if duplicate 
events are caught  [PASS]
  18:16:16 DEBUG| [stdout] # [16] event tracing - enable/disable with event 
level files [PASS]
  18:16:17 DEBUG| [stdout] # [17] event tracing - restricts events based on pid 
notrace filtering       [PASS]
  18:16:18 DEBUG| [stdout] # [18] event tracing - restricts events based on pid 
[PASS]
  TEST SYSTEM FAILURE DETECTED Test results file 
'/home/maas/workspace/jammy-linux-ibm-ibm-amd64-5.15.0-1033.36-s2-janbi-ubuntu_kernel_selftests/kernel-results.xml'
 not found.

  
  Console log also attached

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


-- 
Mailing list: https://launchpad.net/~canonical-ubuntu-qa
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa
More help   : https://help.launchpad.net/ListHelp

Reply via email to