Project

General

Profile

action #108887

[desktop] GNOTE 42 has a new UI

Added by dimstar 3 months ago. Updated 2 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
GraceWang
Category:
Bugs in existing tests
Target version:
-
Start date:
2022-03-24
Due date:
% Done:

100%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-desktopapps-documentation@64bit fails in
gnote_link_note

openSUSE Tumbleweed received GNOME 42 in snapshot 20220323 (timely with the upstream release)
gnote was amongst the applications with larger UI changes, which prompts for test changes.

Test suite description

Maintainer Yaun Ren

Reproducible

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

Expected result

Last good: 20220322 (or more recent)

Further details

Always latest result in this scenario: latest

History

#1 Updated by maritawerner 3 months ago

  • Subject changed from GNOTE 42 has a new UI to [desktop] GNOTE 42 has a new UI

#2 Updated by GraceWang 3 months ago

  • Assignee set to GraceWang

#3 Updated by openqa_review 3 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: desktopapps-documentation
https://openqa.opensuse.org/tests/2291716#step/gnote_link_note/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 28 days if nothing changes in this ticket.

#4 Updated by GraceWang 2 months ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 80

#5 Updated by GraceWang 2 months ago

  • Status changed from In Progress to Resolved
  • % Done changed from 80 to 100

PR got merged and after restarting the failed test suites on osd and o3 we got positive results.
So, set the ticket status to RESOLVED.

Also available in: Atom PDF