Public bug reported:
Issue found on J-oem-6.1 on Intel SDP node "northrup-716346"
Test ftrace:test.d--00basic--basic2.tc will and ftrace:test.d--direct--
ftrace-direct.tc will failed with timeout.
A manual test shows
* ftrace:test.d--00basic--basic2.tc took about 15m14.753s to run
* ftrace:test.d--direct--ftrace-direct.tc took about 120m26.584s to run
The reason behind this is because this SUT has 288 CPU, and it took
about 6 seconds to offline a CPU during the test.
We will need to bump our timeout threshold for this.
** Affects: ubuntu-kernel-tests
Importance: Undecided
Assignee: Po-Hsu Lin (cypressyew)
Status: In Progress
** Tags: 6.1 jammy oem sru-s20240108 ubuntu-kselftests-ftrace
** Changed in: ubuntu-kernel-tests
Status: New => In Progress
--
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/2054789
Title:
ubuntu_kselftests_ftrace tend to timeout on system with huge amount of
CPUs
Status in ubuntu-kernel-tests:
In Progress
Bug description:
Issue found on J-oem-6.1 on Intel SDP node "northrup-716346"
Test ftrace:test.d--00basic--basic2.tc will and ftrace:test.d--direct
--ftrace-direct.tc will failed with timeout.
A manual test shows
* ftrace:test.d--00basic--basic2.tc took about 15m14.753s to run
* ftrace:test.d--direct--ftrace-direct.tc took about 120m26.584s to run
The reason behind this is because this SUT has 288 CPU, and it took
about 6 seconds to offline a CPU during the test.
We will need to bump our timeout threshold for this.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2054789/+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
