Project

General

Profile

Actions

action #18480

closed

[sle][functional]test fails in yast2_snapper

Added by dgutu almost 7 years ago. Updated about 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Start date:
2017-04-10
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario sle-12-SP3-Server-DVD-x86_64-autoyast_sle12_gnome@64bit fails in
yast2_snapper

Reproducible

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

Expected result

Last good: 0315 (or more recent)

Further details

Always latest result in this scenario: latest


Related issues 2 (0 open2 closed)

Related to openQA Tests - action #18346: [sles][functional][yast] yast2_snapper: sporadicly snapshot deletion takes longer - but test is not waiting 240s like in the code anywayRejected2017-04-052018-03-13

Actions
Related to openQA Tests - action #19974: [sles][functional] test fails in yast2_snapper - after a timeout trying to install yast2-snapper, the SUT is waiting for confirmation, causing a timeoutRejectedokurz2017-06-21

Actions
Actions #2

Updated by mkravec almost 7 years ago

  • Status changed from In Progress to Resolved
Actions #3

Updated by dehai almost 7 years ago

  • Status changed from Resolved to In Progress
Actions #4

Updated by okurz over 6 years ago

  • Subject changed from test fails in yast2_snapper to [sle][functional]test fails in yast2_snapper
Actions #5

Updated by okurz over 6 years ago

  • Related to action #18346: [sles][functional][yast] yast2_snapper: sporadicly snapshot deletion takes longer - but test is not waiting 240s like in the code anyway added
Actions #6

Updated by okurz over 6 years ago

  • Related to action #19974: [sles][functional] test fails in yast2_snapper - after a timeout trying to install yast2-snapper, the SUT is waiting for confirmation, causing a timeout added
Actions #7

Updated by okurz over 6 years ago

  • Target version set to Milestone 13
Actions #8

Updated by okurz about 6 years ago

  • Status changed from In Progress to Resolved

I think we can continue the work in tickets with more specific subject, e.g. -> #30619

Actions

Also available in: Atom PDF