action #43634
closed
[functional][u] test fails in force_scheduled_tasks - load is not settled, "sleep" is never a good idea ;)
Added by szarate over 5 years ago.
Updated over 5 years ago.
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 21
Description
Observation¶
openQA test in scenario sle-15-SP1-Installer-DVD-x86_64-allpatterns@svirt-xen-pv fails in
force_scheduled_tasks
Before calling this yet another btrfs issue: I noticed that there's
sleep 3; # some head room for the load average to rise
Right before calling settle load... isn't it better to call sync? How did we get to slee 3?
Reproducible¶
Fails since (at least) Build 88.6 (current job)
Expected result¶
Load is settled and test is able to continue.
- Subject changed from test fails in force_scheduled_tasks - load is not settled to [functional][u] test fails in force_scheduled_tasks - load is not settled, "sleep" is never a good idea ;)
- Status changed from New to Workable
- Target version set to Milestone 21
- Status changed from Workable to In Progress
- Assignee set to zluo
don't care about registration. This ticket is about a sleep in the test module, can be easily tested with a Tumbleweed image and SCHEDULE=tests/boot/boot_to_desktop,tests/console/force_scheduled_tasks and a local isotovideo run. Using full-blown openQA SLE15+allpatterns+registration tests is pure waste and IMHO very inefficient. Just make it easy for yourself :)
- Status changed from In Progress to Feedback
- Status changed from Feedback to Resolved
PR is merged, we already have 100 local runs for verification and this is not introducing any changes to test suites but should be a logical refactoring so resolving.
Also available in: Atom
PDF