Project

General

Profile

Actions

action #60236

open

[opensuse][functional] test fails in plasma_browser_integration on aarch64

Added by ggardet_arm over 4 years ago. Updated about 2 months ago.

Status:
Workable
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario opensuse-Tumbleweed-DVD-aarch64-kde-wayland@aarch64 fails in
plasma_browser_integration

It fails to pause, maybe some retries are needed?

Test suite description

Basic KDE installation, but switches to a Wayland session on login. Needs Virtio (or similiar) GPU.

Reproducible

Fails since (at least) Build 20191109

Expected result

Last good: 20191104 (or more recent)

Further details

Always latest result in this scenario: latest


Related issues 1 (0 open1 closed)

Related to openQA Tests - action #59867: [functional][u] New plasma_browser_integration test is unstableResolvedzluo2019-11-15

Actions
Actions #1

Updated by favogt over 4 years ago

It doesn't look like the system is under heavy load, so I'm not sure why the click got lost.
Maybe it's clicking too early even?

Actions #2

Updated by ggardet_arm over 4 years ago

favogt wrote:

It doesn't look like the system is under heavy load, so I'm not sure why the click got lost.
Maybe it's clicking too early even?

It could be.

Actions #3

Updated by mgriessmeier over 4 years ago

  • Subject changed from test fails in plasma_browser_integration on aarch64 to [functional][u] test fails in plasma_browser_integration on aarch64
Actions #4

Updated by mgriessmeier over 4 years ago

  • Related to action #59867: [functional][u] New plasma_browser_integration test is unstable added
Actions #5

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: kde-wayland
https://openqa.opensuse.org/tests/1136942

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 #6

Updated by zluo over 4 years ago

http://f40.suse.de/tests/6613#next_previous
looks good now with assert_and_click('plasma-browser-integration-install', 120);

Actions #7

Updated by okurz about 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: kde-wayland
https://openqa.opensuse.org/tests/1162264

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 #8

Updated by okurz about 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: kde-wayland
https://openqa.opensuse.org/tests/1188996

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 #9

Updated by SLindoMansilla about 4 years ago

  • Status changed from New to Workable
  • Assignee set to favogt

Hi Fabian, could you take a look?

Actions #10

Updated by favogt about 4 years ago

The system appears to be totally overloaded, so other than increasing the timeout to beyond 5 minutes for loading a single webpage (!) I don't think the module itself can do anything about it.
Even then, it'll probably fail one of the later steps, as it has to play a video in firefox as well.

So not sure what to do.

Actions #11

Updated by okurz about 4 years ago

Well, overloaded could be CPU, could be IO, could be RAM, potentially could also be the environment in which the VM is running. Hence I suggest to investigate which of the factor it is.

Actions #12

Updated by tjyrinki_suse over 3 years ago

  • Subject changed from [functional][u] test fails in plasma_browser_integration on aarch64 to [qe-core][functional] test fails in plasma_browser_integration on aarch64
Actions #13

Updated by tjyrinki_suse about 3 years ago

  • Subject changed from [qe-core][functional] test fails in plasma_browser_integration on aarch64 to [opensuse][functional] test fails in plasma_browser_integration on aarch64
  • Start date deleted (2019-11-25)

Still happens :( Tagging only opensuse however, our squad does contribute as best effort but this is not part of SLE.

Actions #14

Updated by slo-gin over 1 year ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions #15

Updated by slo-gin about 2 months ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions

Also available in: Atom PDF