ftrace test timed out on Cosmic P8

Bug #1813531 reported by Po-Hsu Lin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
Fix Released
Medium
Po-Hsu Lin

Bug Description

It took about 17 minute to finish the ftrace test in ubuntu_kernel_selftests:

  [58] (instance) event trigger - test multiple histogram triggers [PASS]
  [59] (instance) trace_marker trigger - test snapshot trigger [PASS]

  # of passed: 59
  # of failed: 0
  # of unresolved: 0
  # of untested: 0
  # of unsupported: 0
  # of xfailed: 0
  # of undefined(test bug): 0
  6.26user 50.41system 16:20.26elapsed 5%CPU (0avgtext+0avgdata 6016maxresident)k

With the current setting, the test will get killed:
 [44] trace_marker trigger - test histogram with synthetic event against kernel event [PASS]
 [45] trace_marker trigger - test histogram with synthetic event [PASS]
 [46] event trigger - test traceon/off trigger [PASS]
 [47] (instance) Basic test for tracers [PASS]
 Timer expired (900 sec.), nuking pid 35498
 ERROR ubuntu_kernel_selftests.ftrace ubuntu_kernel_selftests.ftrace timestamp=1548649668 localtime=Jan 28 04:27:48 Test timeout expired, rc=15

We need to adjust the timeout setting.

Po-Hsu Lin (cypressyew)
Changed in ubuntu-kernel-tests:
status: New → In Progress
assignee: nobody → Po-Hsu Lin (cypressyew)
importance: Undecided → Medium
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

We have some test disabled,

https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=a02ccfa8d9f5e311bc22b0c091ea1e26b7daf4ec

Need to retest this to see if it will still times out.

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

With that test disabled in comment #1, it still took about >15 minutes to run.

So yes we need to enlarge the timeout threshold.

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Changed in ubuntu-kernel-tests:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.