action #53969
closed[sle][y][functional][arm][sporadic] test fails in yast2_clone_system - cloning takes more time than expected
0%
Description
Observation¶
We should take a look if there is any reasonable explanation of the delay and bump the timeout to stabilize the test runs.
openQA test in scenario sle-12-SP5-Server-DVD-aarch64-clone_system@aarch64 fails in
yast2_clone_system
Test suite description¶
Maintainer: okurz@suse.de
Clone the system into an autoyast profile to be used by downstream jobs, e.g. to test reinstall from that profile.
Reproducible¶
Fails since (at least) Build 0216 (current job)
Expected result¶
Last good: 0214 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by riafarov over 4 years ago
- Due date set to 2019-08-13
- Target version set to Milestone 26
We have already bumped the timeout, so worth having a closer look. To figure out the root cause.
Updated by riafarov over 4 years ago
- Subject changed from [sle][y][functional][arm] test fails in yast2_clone_system - cloning takes more time than expected to [sle][y][functional][arm][sporadic] test fails in yast2_clone_system - cloning takes more time than expected
- Description updated (diff)
- Status changed from New to Workable
- Estimated time set to 3.00 h
Updated by JRivrain over 4 years ago
- This happened every 2 second run when this one was signaled, but has not happened since then in the past 6 builds. May as well not happen anymore.
In the failed runs, the serial-terminal.txt only contains this:
Welcome to SUSE Linux Enterprise Server 12 SP5 Beta2 (aarch64) - Kernel 4.12.14-100-default (hvc0).
susetest login:
and that's all. However I don't see why this would be related yet, in serial0.txt we have "yast2-clone_system-status-0" even in failed runs, it looks like the message was not intercepted.
Updated by JRivrain over 4 years ago
- Status changed from Workable to In Progress
Updated by JRivrain over 4 years ago
- Status changed from In Progress to Blocked
Blocked by https://progress.opensuse.org/issues/54869: it cannot be cloned because parent job fails almost every time.
Updated by JERiveraMoya over 4 years ago
Parent job seems to be running today: https://openqa.suse.de/tests/3203400. ~Let's see if succeeds creating the image.~ far from that unfortunately.
Updated by JRivrain over 4 years ago
- Assignee deleted (
JRivrain)
De-assigning myself. could not work on it because of https://bugzilla.suse.com/show_bug.cgi?id=1058375 and https://progress.opensuse.org/issues/54869, and I am leaving for two weeks.
Updated by okurz over 4 years ago
- Status changed from Blocked to Workable
- Priority changed from Normal to High
Both the mentioned tickets are certainly an impediment but should not be a blocker as the issue is reproducible at least within the OSD based tests, see the latest https://openqa.suse.de/tests/3205919#step/yast2_clone_system/4 . Ok for you to unset blocked status?
Updated by oorlov over 4 years ago
- Status changed from Workable to In Progress
- Assignee set to oorlov
Updated by oorlov over 4 years ago
I've created WIP PR with the increased timeout and started 40 runs: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/8109