Project

General

Profile

Actions
Copy link

action #38336

closed

[functional][u] Re-enable yast2_snapper on openSUSE

Added by okurz over 6 years ago. Updated about 6 years ago.

Status:
Resolved
Priority:
High
Assignee:
dheidler
Category:
Bugs in existing tests
Target version:
SUSE QA (private) - Milestone 20
Start date:
2018-07-10
Due date:
2018-10-23
% Done:

0%

Estimated time:
Difficulty:

Description

Motivation

lnussel disabled yast2_snapper from openSUSE with c3ae9ea0 . (IMHO with this jeopardizing the quality of openSUSE products given how many problems we have in the product related to snapper). We should bring it back.

Acceptance criteria

  • AC1: yast2_snapper and yast2_snapper_ncurses run again in a stable manner in common openSUSE scenarios, e.g. openSUSE Tumbleweed and openSUSE Leap -> AT1-1: 10 jobs in a row do not fail in yast2_snapper or yast2_snapper_ncurses, AT1-2: same as AT1-1 for Leap

Suggestions

  • In lib/main_common.pm:snapper_is_applicable include openSUSE again
  • Test it locally on openSUSE Tumbleweed or Leap
  • Ensure tests have all necessary needles and pass
  • Ensure the same for the second openSUSE distribution
  • Ensure good statistics, see ATs

Related issues 3 (0 open — 3 closed)

Related to openQA Tests (public) - coordination #35032: [functional][opensuse][epic][y] Make snapper tests easier to maintainResolvedriafarov2018-04-16

Actions
Related to openQA Tests (public) - action #42635: [functional][y] test fails in upgrade_snapshots - snapper output format changedResolvedJERiveraMoya2018-10-172018-11-06

Actions
Blocks openQA Tests (public) - action #30619: [sle][functional][y][medium][bsc#1032831] test fails in yast2_snapper after closing the main GUI window - do we need to bringback the original workaround? or improve loggingResolvedokurz2018-01-222019-03-26

Actions
Actions
Copy link

Also available in: Atom PDF