action #57212
closed
[functional][u][sporadic] test fails in bootloader - Timed out waiting for installer to start
Added by SLindoMansilla over 4 years ago.
Updated over 4 years ago.
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 28
Description
Observation¶
Timed out waiting for installer to start.
Does the time out need to be increased?
Tasks¶
- Verify is the loading portion is still running
- Extend the timeout another two minutes
Reproducible¶
Expected result¶
Last good: 0322
Further details¶
Always latest result in this scenario: latest
- Subject changed from [functional][u] test fails in bootloader - Timed out waiting for installer to start to [functional][u][sporadic] test fails in bootloader - Timed out waiting for installer to start
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: default@ppc64le-spvm
https://openqa.suse.de/tests/3495951
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: textmode@ppc64le-spvm
https://openqa.suse.de/tests/3507113
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: textmode@ppc64le-spvm
https://openqa.suse.de/tests/3576118
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
- Description updated (diff)
- Status changed from New to Workable
- Target version set to Milestone 28
- Estimated time set to 42.00 h
- Status changed from Workable to In Progress
- Assignee set to zluo
take over and check current status.
I think this is somehow related to #55406.
consider to increase 60 to 120 in bootloader_spvm.pm
assert_screen("run-yast-ssh", 120);
I'll test this anyway and collect some statics for this change.
looks good as well on osd.
- Status changed from In Progress to Feedback
PR updated and asked for review now.
- Status changed from Feedback to Resolved
Also available in: Atom
PDF