Project

General

Profile

Actions
Copy link

action #66149

closed

[desktop][u] seahorse 3.36 needs test adjustments

Added by dimstar over 4 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
zluo
Category:
Bugs in existing tests
Target version:
SUSE QA (private) - Milestone 30
Start date:
2020-04-28
Due date:
% Done:

0%

Estimated time:
42.00 h
Difficulty:

Description

Observation

The test needs to be adjusted to interact properly with seahorse 3.36

seahorse was previously opened at the main panel. Since it fails, it is opened in the sub-panel "GPG keys". (product bug?)

Acceptance criteria

  • AC1: seahorse passes or soft-fail on a product bug

Suggestions

  • Investigate why seahorse opens in the sub-panel "GPG keys" and figure out if it is a test bug or a product bug

Reproducible

  • Fails in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_on_gnome@64bit
  • Current occurrence: 20200815
  • Last good: 20200329
  • latest

Related issues 1 (1 open — 0 closed)

Related to openQA Tests (public) - action #89422: [opensuse] test fails in seahorse starting with keyring lock screen for ppc64leNew

Actions
Actions
Copy link
 #1

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: extra_tests_on_gnome
https://openqa.opensuse.org/tests/1264772

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
Copy link
 #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: extra_tests_on_gnome
https://openqa.opensuse.org/tests/1279564

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
Copy link
 #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: extra_tests_on_gnome
https://openqa.opensuse.org/tests/1294372

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
Copy link
 #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: extra_tests_on_gnome
https://openqa.opensuse.org/tests/1312450

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
Copy link
 #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: extra_tests_on_gnome
https://openqa.opensuse.org/tests/1328349

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

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: extra_tests_on_gnome
https://openqa.opensuse.org/tests/1339737

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
Copy link
 #7

Updated by SLindoMansilla over 4 years ago

  • Subject changed from seahorse 3.36 needs test adjustments to [desktop][u] seahorse 3.36 needs test adjustments
  • Description updated (diff)
Actions
Copy link
 #8

Updated by SLindoMansilla over 4 years ago

  • Status changed from New to Workable
  • Target version set to Milestone 30
  • Estimated time set to 42.00 h
Actions
Copy link
 #9

Updated by zluo over 4 years ago

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

take over

Actions
Copy link
 #10

Updated by zluo over 4 years ago

http://10.162.23.47/tests/7993#step/seahorse/14

I find out: seahorse is locked and it requires an unlock, this is difference than it on sled. At least this is new issue.

The problem is after Unlock it doesn't display entries of passwords (Login), Keys(GPG Keys), Certificates (Default Trust).
I think I can report this as bug for now.

Actions
Copy link
 #13

Updated by zluo over 4 years ago

https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/10854
will test my PR on O3 later when needle PR got merged.

Actions
Copy link
 #14

Updated by zluo over 4 years ago

needle pr merged now. check verification on O3 later:

https://openqa.opensuse.org/tests/1371087

Actions
Copy link
 #15

Updated by zluo over 4 years ago

  • Status changed from In Progress to Resolved
Actions
Copy link
 #16

Updated by michel_mno almost 4 years ago

  • Related to action #89422: [opensuse] test fails in seahorse starting with keyring lock screen for ppc64le added
Actions
Copy link

Also available in: Atom PDF