Possibly the same issue observed on s2024.12.02/bionic/linux-
hwe-5.4/5.4.0-205.225~18.04.1 on tf amd-server.
The old console output from 2024.01.08 (see bug description) seems no
longer accesible, so I cannot confirm if it's exactly the same. Below is
the output from s2024.12.02 linux-hwe-5.4 on tf amd-server:
[...]
+ echo make sure it only works 3 times
make sure it only works 3 times
+ echo 0
+ sleep .1
+ echo schedule:enable_event:sched:sched_switch:3
+ seq 3
+ sleep .1
+ echo test 1
test 1
+ test_event_enabled 1*
+ val=1*
+ check_times=10
+ [ 10 -ne 0 ]
+ cat events/sched/sched_switch/enable
+ e=1*
+ [ 1* = 1* ]
+ return 0
+ echo 0
+ sleep .1
+ echo test 2
test 2
+ test_event_enabled 1*
+ val=1*
+ check_times=10
+ [ 10 -ne 0 ]
+ cat events/sched/sched_switch/enable
+ e=1*
+ [ 1* = 1* ]
+ return 0
+ echo 0
+ sleep .1
+ echo test 3
test 3
+ test_event_enabled 1*
+ val=1*
+ check_times=10
+ [ 10 -ne 0 ]
+ cat events/sched/sched_switch/enable
+ e=0*
+ [ 0* = 1* ]
+ sleep .1
+ check_times=9
+ [ 9 -ne 0 ]
+ cat events/sched/sched_switch/enable
+ e=0*
+ [ 0* = 1* ]
+ sleep .1
+ check_times=8
+ [ 8 -ne 0 ]
+ cat events/sched/sched_switch/enable
+ e=0*
+ [ 0* = 1* ]
+ sleep .1
+ check_times=7
+ [ 7 -ne 0 ]
+ cat events/sched/sched_switch/enable
+ e=0*
+ [ 0* = 1* ]
+ sleep .1
+ check_times=6
+ [ 6 -ne 0 ]
+ cat events/sched/sched_switch/enable
+ e=0*
+ [ 0* = 1* ]
+ sleep .1
+ check_times=5
+ [ 5 -ne 0 ]
+ cat events/sched/sched_switch/enable
+ e=0*
+ [ 0* = 1* ]
+ sleep .1
+ check_times=4
+ [ 4 -ne 0 ]
+ cat events/sched/sched_switch/enable
+ e=0*
+ [ 0* = 1* ]
+ sleep .1
+ check_times=3
+ [ 3 -ne 0 ]
+ cat events/sched/sched_switch/enable
+ e=0*
+ [ 0* = 1* ]
+ sleep .1
+ check_times=2
+ [ 2 -ne 0 ]
+ cat events/sched/sched_switch/enable
+ e=0*
+ [ 0* = 1* ]
+ sleep .1
+ check_times=1
+ [ 1 -ne 0 ]
+ cat events/sched/sched_switch/enable
+ e=0*
+ [ 0* = 1* ]
+ sleep .1
+ check_times=0
+ [ 0 -ne 0 ]
+ fail Expected 1* but found 0*
+ echo Expected 1* but found 0*
Expected 1* but found 0*
+ exit_fail
+ exit 1
--
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/2052476
Title:
func_event_triggers.tc from ubuntu_kselftests_ftrace failed with "fail
Expected 1* but found 0*"
Status in ubuntu-kernel-tests:
New
Bug description:
func_event_trigger.tc fails in ubuntu_kselftests_ftrace with "fail
Expected 1* but found 0*" for focal riscv-5.15 for SRU cycle
2024.01.08.
link to console output for test failure:
http://10.246.75.167/2024.01.08/focal/linux-
riscv-5.15/5.15.0-1049.53~20.04.2/sru-generic-metal-
riscv64-focal-515.riscv64-ubuntu_kselftests_ftrace-
log.html#ftrace:test.d--ftrace--func_event_triggers.tc-start
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2052476/+subscriptions
--
Mailing list: https://launchpad.net/~canonical-ubuntu-qa
Post to : canonical-ubuntu-qa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa
More help : https://help.launchpad.net/ListHelp
