Project

General

Profile

Actions

action #92095

closed

[qe-core][tumbleweed] test fails in multi_users_dm, string typed in gnome search rather than xterm screen

Added by michel_mno about 3 years ago. Updated 15 days ago.

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

100%

Estimated time:
Difficulty:

Description

Observation

test fails in multi_users_dm, string typed in gnome search rather than xterm screen
since TW 20210429.
I do not know why.

openQA test in scenario opensuse-Tumbleweed-DVD-ppc64le-extra_tests_gnome@ppc64le fails in
multi_users_dm

Test suite description

Maintainer: QE Core, asmorodskyi. Extra tests which were designed to run on gnome

Reproducible

Fails since (at least) Build 20210207

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest

Actions #1

Updated by openqa_review about 3 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_gnome
https://openqa.opensuse.org/tests/1745143

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

Updated by maritawerner about 3 years ago

  • Subject changed from test fails in multi_users_dm, string typed in gnome search rather than xterm screen to [qe-core] test fails in multi_users_dm, string typed in gnome search rather than xterm screen
Actions #3

Updated by tjyrinki_suse almost 3 years ago

  • Subject changed from [qe-core] test fails in multi_users_dm, string typed in gnome search rather than xterm screen to [qe-core][tumbleweed] test fails in multi_users_dm, string typed in gnome search rather than xterm screen
  • Status changed from New to Workable
  • Start date deleted (2021-05-03)
Actions #4

Updated by punkioudi almost 3 years ago

  • Status changed from Workable to In Progress
  • Assignee set to punkioudi
Actions #5

Updated by punkioudi almost 3 years ago

Small update :

  • When the user re logs in, the gnome generic desktop gets unfocused. When the user opens the xterm, this is also unfocused and consequently when the user types a command, it is seems typed in gnome search. This was also reproduced in TW with x86_64 arch and it is apparently a gnome product [bug]
  • For this reason, I will soft-fail it, do a workaround and keep the test running.
  • One more thing that was noticed (kudos to @szarate) is that this [needle] is not valid, as at this step the generic desktop should be focused :) . For this reason, it will be removed.
Actions #7

Updated by punkioudi almost 3 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100
Actions #8

Updated by szarate almost 3 years ago

  • Target version set to QE-Core: Ready
Actions #9

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

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
Actions #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: extra_tests_gnome
https://openqa.opensuse.org/tests/2131561

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
Actions #11

Updated by okurz over 2 years ago

  • Status changed from Resolved to Feedback

^

Actions #12

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

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
Actions #13

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

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
Actions #14

Updated by openqa_review 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: extra_tests_gnome
https://openqa.opensuse.org/tests/2207023

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
Actions #15

Updated by tjyrinki_suse about 2 years ago

  • Target version deleted (QE-Core: Ready)

As this was reopened, it's not in sprint backlog, but in product backlog.

Actions #16

Updated by openqa_review 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: extra_tests_gnome
https://openqa.opensuse.org/tests/2324312#step/multi_users_dm/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 76 days if nothing changes in this ticket.

Actions #17

Updated by openqa_review 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: extra_tests_gnome
https://openqa.opensuse.org/tests/2499560#step/multi_users_dm/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 188 days if nothing changes in this ticket.

Actions #18

Updated by punkioudi over 1 year ago

  • Assignee deleted (punkioudi)
Actions #19

Updated by slo-gin 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 #20

Updated by mgrifalconi 15 days ago

  • Tags set to qecore-cleanup
  • Status changed from Feedback to Rejected

links are broken and ticket is quite old. Please reopen with current examples if still current

Actions

Also available in: Atom PDF