Improve test granularity of ubuntu_kselftests_ftrace
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ubuntu-kernel-tests |
In Progress
|
Undecided
|
Po-Hsu Lin | ||
Bug Description
Currently we have just a "setup", "ftrace-build" and "ftracetest" inside this test suite.
All ~100 sub test cases are being testing under the "ftracetest" test case. There is a summary in the end of the report, but test reviewer still need to look into the detail and search for failing sub-tests.
Especially we have a flaky traceon/off test that's failing from time to time (bug 1837040), we have this issue hinted, but it’s unsafe to make it a permanent hint as ftracetest contains around 100 tests. If we hint it directly we might have some regression slipped through.
It will be great to break them down. So that we can see which test case is failing right from the "Cases" section on the test report page. And we can hint the failing one more precisely and without interfering other tests.
Related branches
- Sean Feole: Approve
- Francis Ginther: Approve
-
Diff: 95 lines (+22/-40)2 files modifiedubuntu_kselftests_ftrace/control (+18/-28)
ubuntu_kselftests_ftrace/ubuntu_kselftests_ftrace.py (+4/-12)
| description: | updated |
| description: | updated |
| Po-Hsu Lin (cypressyew) wrote | #1 |
| Po-Hsu Lin (cypressyew) wrote | #2 |
Test result (failed tests cases) with 30 min timeout on node janbi with J-realtime.