Project

General

Profile

Actions
Copy link

action #101292

closed

[Timebox: 16h] Investigate test fails in consoletest_finish and shutdown

Added by JRivrain about 3 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
syrianidou_sofia
Target version:
Current
Start date:
2021-10-21
Due date:
% Done:

0%

Estimated time:

Description

Observation

This happens every second run, in that specific test suite and only on ppc64le. The needle "login_screen-typed_password" is seen but yet the key "ret" does not seem to be caught by SUT.
See code here https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/bc535976e2643fc618850fd921beac3d54934378/lib/x11utils.pm#L140-L139

openQA test in scenario sle-15-SP4-Full-ppc64le-offline_install+skip_registration@ppc64le fails in
consoletest_finish

Test suite description

Maintainer: riafarov

Offline installation. Skipping registration for SLE 15, as requires network connection. This is default behavior for SLE 12.

Reproducible

Fails since (at least) Build 50.1

Expected result

Last good: 47.1 (or more recent)

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by JRivrain about 3 years ago

  • Project changed from openQA Tests (public) to qe-yam
  • Category deleted (Bugs in existing tests)
Actions
Copy link
 #2

Updated by JRivrain about 3 years ago

  • Subject changed from test fails in consoletest_finish to test fails in consoletest_finish and shutdown
Actions
Copy link
 #3

Updated by rainerkoenig about 3 years ago

Can this be another occurence of the https://bugzilla.suse.com/show_bug.cgi?id=1191112 glitch?

Actions
Copy link
 #4

Updated by syrianidou_sofia about 3 years ago

  • Status changed from New to In Progress
  • Assignee set to syrianidou_sofia
Actions
Copy link
 #5

Updated by JERiveraMoya about 3 years ago

  • Target version set to Current
Actions
Copy link
 #6

Updated by JERiveraMoya about 3 years ago

  • Subject changed from test fails in consoletest_finish and shutdown to [Timebox: 8h] Investigate test fails in consoletest_finish and shutdown
  • Priority changed from High to Normal

We could try to increase timeout here, apparently it matches afterwards: https://openqa.suse.de/tests/7500012#step/consoletest_finish/25
But for the other cases I can see it is not clear, we need to investigate and communicate finding to desktop team.

Actions
Copy link
 #7

Updated by JERiveraMoya about 3 years ago

  • Subject changed from [Timebox: 8h] Investigate test fails in consoletest_finish and shutdown to [Timebox: 16h] Investigate test fails in consoletest_finish and shutdown
Actions
Copy link
 #8

Updated by syrianidou_sofia about 3 years ago

The failure is spotted mostly for ppc64le (2/10 runs I did without any code changes) and spotted only once so far, for x86_64. The failure for consoletest_finish seems to be happening on two different occasions:

The first failure can be tackled by increasing the assert_screen timeout for ensure_unlocked_desktop function in lib/x11utils.pm L:125.
PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/13678 (initially tried 100sec but wasn't enough)

The second failure seems to be related to bug#1168979, which is open for more than a year now, so it could be handled by a soft failure like here: https://openqa.suse.de/tests/7618984#step/consoletest_finish/20. Creating a new workaround needle linked to the bug, is not acceptable by qe-core team because it would appear for s390x too and we are not 100% sure if it is related to the bug or it's worker slowness. Also, creating a new needle for ppc64le, similar to the one for s390x causes issue lik ethis one : https://openqa.suse.de/tests/7697165#step/consoletest_finish/21 . So this needs a more complicated solution.

P.S. Interesting info were provided in #eng-testing : https://suse.slack.com/archives/C02CANHLANP/p1634725917340200?thread_ts=1634723632.337400&cid=C02CANHLANP

Actions
Copy link
 #9

Updated by syrianidou_sofia about 3 years ago

  • Status changed from In Progress to Feedback
Actions
Copy link
 #10

Updated by openqa_review over 2 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: offline_install+skip_registration
https://openqa.suse.de/tests/8556950#step/consoletest_finish/1

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" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

Actions
Copy link
 #11

Updated by JERiveraMoya over 2 years ago

  • Status changed from Feedback to Closed

We decided to move to PowerVM and avoid this unsupported scenarios.

Actions
Copy link

Also available in: Atom PDF