Project

General

Profile

action #88147

[desktop][sle15sp3] test fails in thunderbird_pop

Added by zcjia over 2 years ago. Updated 10 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2021-01-22
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

The behavior of thunderbird "Protocol" changed, original code
assert_screen 'thunderbird_wizard-imap-pop-open';
send_key 'down';
send_key 'ret';
doesn't work (requires an extra 'down').

I propose to change it to assert_and_click 'thunderbird_wizard-imap-pop-open'.

openQA test in scenario sle-15-SP3-Online-x86_64-wayland-desktopapps-message@64bit-virtio-vga fails in
thunderbird_pop

Test suite description

Reproducible

Fails since (at least) Build 129.9

Expected result

Last good: 127.1 (or more recent)

Further details

Always latest result in this scenario: latest

History

#1 Updated by zcjia over 2 years ago

#2 Updated by zcjia over 2 years ago

Fails again for build 154.1: https://openqa.suse.de/tests/5546230#step/thunderbird_pop/7

So this problem still needs to be fixed after all.

#3 Updated by okurz about 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: wayland-desktopapps-message
https://openqa.suse.de/tests/5662436

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

#4 Updated by okurz about 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: wayland-desktopapps-message
https://openqa.suse.de/tests/5702119

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

#5 Updated by okurz about 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: wayland-desktopapps-message
https://openqa.suse.de/tests/5815637

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

#6 Updated by okurz about 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: wayland-desktopapps-message
https://openqa.suse.de/tests/5900078

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

#7 Updated by okurz about 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: wayland-desktopapps-message
https://openqa.suse.de/tests/5990758

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

#8 Updated by okurz almost 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: wayland-desktopapps-message
https://openqa.suse.de/tests/5981010

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

#9 Updated by slo-gin 10 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.

#10 Updated by zcjia 10 months ago

  • Status changed from New to Resolved

Fixed in thunderbird_common.pm.

Also available in: Atom PDF