Project

General

Profile

Actions

action #65262

closed

[functional][u] Firstboot test fails on GDM screen (expects gnome-session)

Added by lkocman about 4 years ago. Updated almost 4 years ago.

Status:
Rejected
Priority:
Normal
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 30
Start date:
2020-04-03
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Firstboot test fails on GDM screen (expects gnome-session)

Observation

openQA test in scenario opensuse-15.2-NET-x86_64-gnome@Laptop_64 fails in
first_boot

Test suite description

Reproducible

Fails since (at least) Build 619.3 (current job)

Expected result

Last good: 619.2 (or more recent)

Further details

Always latest result in this scenario: latest

Actions #2

Updated by okurz about 4 years ago

  • Subject changed from Firstboot test fails on GDM screen (expects gnome-session) to [functional][u] Firstboot test fails on GDM screen (expects gnome-session)

please try to put your custom text within sections of the text not above and feel free to adjust the template text to your liking. Also I recommend you find a team tag or assign to the test module maintainer.

Actions #3

Updated by okurz almost 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: upgrade_Leap_42.3_cryptlvm@uefi
https://openqa.opensuse.org/tests/1244032

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

Updated by okurz almost 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: upgrade_Leap_42.3_cryptlvm@uefi
https://openqa.opensuse.org/tests/1262358

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

Updated by SLindoMansilla almost 4 years ago

  • Status changed from New to Rejected
  • Assignee set to SLindoMansilla
  • Target version set to Milestone 30

It was actually a product bug.
And it is not reproducible since 12 days: https://openqa.opensuse.org/tests/1270455#next_previous

Actions #6

Updated by okurz almost 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: upgrade_Leap_42.1_gnome
https://openqa.opensuse.org/tests/1289806

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

Updated by okurz almost 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: upgrade_Leap_42.1_gnome
https://openqa.opensuse.org/tests/1307914

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

Also available in: Atom PDF