action #31510
closed[sle][functional][easy][fast] test fails in execute_test_run - Copy process is taking much more time now
0%
Description
Observation¶
openQA test in scenario sle-15-Installer-DVD-s390x-fs_stress@s390x-kvm-sle12 fails in
execute_test_run
Investigate why copy process is taking much more time now comparing with previous builds. It could be a bug related with memory or the test might need to be adapted increasing timeout for the operation.
This ticket is only about a quick investigation, cloning the job and checking the memory. Create a bug if not apparent issue is found.
Reproducible¶
Fails since (at least) Build 446.2 (current job)
Expected result¶
Last good: 444.1 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by JERiveraMoya about 6 years ago
- Subject changed from [sle][functional] test fails in execute_test_run - Copy process is taking much more time now to [sle][functional][easy] test fails in execute_test_run - Copy process is taking much more time now
- Description updated (diff)
Updated by okurz about 6 years ago
- Subject changed from [sle][functional][easy] test fails in execute_test_run - Copy process is taking much more time now to [sle][functional][easy][fast] test fails in execute_test_run - Copy process is taking much more time now
- Due date set to 2018-02-27
Updated by riafarov about 6 years ago
- Status changed from New to In Progress
- Assignee set to riafarov
Updated by riafarov about 6 years ago
- Status changed from In Progress to Feedback
We had an issue with storage on s390x starting from 28-th which may explain such performance degradation. Latest jobs are failing due to a missing cron daemon, so image is not created. Put on feedback to see if reoccurs.
Updated by riafarov about 6 years ago
- Status changed from Feedback to Blocked
Infrastructure issues are blocking the runs.
Updated by riafarov about 6 years ago
- Due date changed from 2018-02-27 to 2018-03-13
Let's see if situation gets better during next spring (it should)
Updated by riafarov about 6 years ago
- Status changed from Blocked to Resolved
Issue was not there for a month, resolving. Feel free to reopen if problem occurs again.