Project

General

Profile

Actions

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.

Status:
Resolved
Priority:
High
Assignee:
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 28
Start date:
2019-09-23
Due date:
% Done:

0%

Estimated time:
42.00 h
Difficulty:

Description

Observation

Timed out waiting for installer to start.
Does the time out need to be increased?

Tasks

  1. Verify is the loading portion is still running
  2. Extend the timeout another two minutes

Reproducible

Expected result

Last good: 0322

Further details

Always latest result in this scenario: latest

Actions #1

Updated by SLindoMansilla over 4 years ago

  • 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
Actions #2

Updated by okurz over 4 years ago

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:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions #3

Updated by okurz over 4 years ago

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:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions #4

Updated by okurz over 4 years ago

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:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions #5

Updated by SLindoMansilla over 4 years ago

  • Description updated (diff)
  • Status changed from New to Workable
  • Target version set to Milestone 28
  • Estimated time set to 42.00 h
Actions #6

Updated by zluo over 4 years ago

  • Status changed from Workable to In Progress
  • Assignee set to zluo

take over and check current status.

Actions #7

Updated by zluo over 4 years ago

it looks stable recently in last month.

need more test runs however. check https://openqa.suse.de/tests/3608168

Actions #8

Updated by zluo over 4 years ago

I think this is somehow related to #55406.

Actions #9

Updated by zluo over 4 years ago

50 test runs:

https://openqa.suse.de/tests/3608178#next_previous

checked, all tests runs are successful.

Actions #10

Updated by zluo over 4 years ago

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.

Actions #12

Updated by zluo over 4 years ago

looks good, let me have some statics: https://openqa.suse.de/tests/3610350#next_previous

Actions #13

Updated by zluo over 4 years ago

looks good as well on osd.

Actions #14

Updated by zluo over 4 years ago

  • Status changed from In Progress to Feedback

PR updated and asked for review now.

Actions #15

Updated by zluo over 4 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF