Project

General

Profile

Actions

action #32956

closed

[sle][functional][u][medium] test fails in yast2_snapper - Improve logging

Added by JERiveraMoya almost 7 years ago. Updated over 6 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Enhancement to existing tests
Target version:
SUSE QA (private) - Milestone 18
Start date:
2018-03-09
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario sle-15-Installer-DVD-aarch64-allpatterns@aarch64 fails in
yast2_snapper

We need to improve logging in this test in order to reproduce the problem https://bugzilla.suse.com/show_bug.cgi?id=1083520 https://bugzilla.suse.com/show_bug.cgi?id=1032831. Test take a lot to be executed, snapshots are not available in openQA for ARM and when command is "strace", this is basically to hack the test, adding development module to have strace available and changing the snapshots and then our needles fails with the list of snapshot. We need to find a better way improve logging in this test.

Reproducible

Fails since (at least) Build 489.1

Expected result

Last good: 486.4 (or more recent)

Further details

Always latest result in this scenario: latest


Related issues 5 (0 open5 closed)

Related to openQA Project (public) - action #19836: [tools]test fails in yast2_snapper - failed to assert serial output - ppc64 and aarch64Resolvedokurz2017-06-14

Actions
Related to openQA Tests (public) - action #17924: [migration] test fails in yast2_snapper trying to delete files -> increase timeout ?Rejected2017-03-23

Actions
Related to openQA Tests (public) - action #19236: [migration]yast2_snapper - failed to "Create New Snapshot"Rejected2017-05-19

Actions
Related to openQA Tests (public) - action #31762: [sle][migration][sle15] test fails in yast2_snapper - check the Low Disk Space warningResolvedqmsu2018-02-14

Actions
Is duplicate of 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 #1

Updated by okurz almost 7 years ago

  • Related to 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 logging added
Actions #2

Updated by okurz almost 7 years ago

  • Related to action #19836: [tools]test fails in yast2_snapper - failed to assert serial output - ppc64 and aarch64 added
Actions #3

Updated by okurz almost 7 years ago

  • Related to action #17924: [migration] test fails in yast2_snapper trying to delete files -> increase timeout ? added
Actions #4

Updated by okurz almost 7 years ago

  • Related to action #19236: [migration]yast2_snapper - failed to "Create New Snapshot" added
Actions #5

Updated by okurz almost 7 years ago

  • Related to action #31762: [sle][migration][sle15] test fails in yast2_snapper - check the Low Disk Space warning added
Actions #6

Updated by okurz almost 7 years ago

  • Subject changed from [sle][functional] test fails in yast2_snapper - Improve logging to [sle][functional][u][medium] test fails in yast2_snapper - Improve logging
  • Target version set to Milestone 18
Actions #7

Updated by okurz over 6 years ago

  • Related to deleted (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 logging)
Actions #8

Updated by okurz over 6 years ago

  • Is duplicate of 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 logging added
Actions #9

Updated by okurz over 6 years ago

  • Status changed from New to Rejected

Actually I consider this a duplicate of #30619 . We already and still have some failure investigation in the code for the original bug bsc#1032831 and if at all about "improve logging" then we should do that in #30619

Actions #10

Updated by okurz over 6 years ago

  • Target version changed from Milestone 18 to Milestone 18
Actions

Also available in: Atom PDF