action #58811
closed
[sle][functional][u]test fails in zypper_lifecycle: testsuite exceeds MAX_JOB_TIME
Added by dheidler over 4 years ago.
Updated over 4 years ago.
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 28
Description
Observation¶
openQA test in scenario sle-15-SP2-Installer-DVD-ppc64le-textmode@ppc64le fails in
zypper_lifecycle
Tasks¶
- Get statistics of failure ratio.
Reproducible¶
Fails since (at least) Build 72.1 (current job)
Expected result¶
Last good: 67.1 (or more recent)
Further details¶
Always latest result in this scenario: latest
Tasks¶
adjust MAX_JOB_TIME so that test won't fail due to MAX_JOB_TIME got exceeded.
- Subject changed from test fails in zypper_lifecycle: testsuite exceeds MAX_JOB_TIME to [sle][functional][u]test fails in zypper_lifecycle: testsuite exceeds MAX_JOB_TIME
- Description updated (diff)
- Status changed from New to Workable
- Description updated (diff)
- Priority changed from High to Normal
- Target version set to Milestone 28
- Estimated time set to 42.00 h
- Status changed from Workable to In Progress
- Assignee set to zluo
- Status changed from In Progress to Rejected
100 test runs, no issue with MAX_JOB_TIME at all, only performance issue with ppcle64 workers. A couple of tests failed sporadic.
- Status changed from Rejected to In Progress
Hi zluo, from https://openqa.suse.de/tests/3526636#next_previous you can see that the job is mostly fine however nears the limit of 2h. The job can take longer in some cases and MAX_JOB_TIME should cover for this. Also especially in cases of post_fail_hooks the time taken can increase as well. I recommend you increase MAX_JOB_TIME in general for the test suite "textmode" regardless of the architecture, e.g. 14400 instead of the default which corresponds to 7200.
- Status changed from In Progress to Resolved
Also available in: Atom
PDF