Project

General

Profile

Actions
Copy link

action #34777

closed

[sle][functional][u][fast][easy] test fails in kdump_and_crash - zypper rm ruby2.1-rubygem-nokogiri NOT FOUND

Added by SLindoMansilla about 7 years ago. Updated almost 7 years ago.

Status:
Resolved
Priority:
High
Assignee:
SLindoMansilla
Category:
Bugs in existing tests
Target version:
SUSE QA (private) - Milestone 17
Start date:
2018-04-12
Due date:
2018-07-03
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

A change in the test made that issue happened on 12-SP3 already. It seems to not be fixed for SP4.

Acceptance criteria

  • AC: ruby2.1-rubygem-nokogiri is only removed if installed

Tasks

  1. Use zypper se -six ruby2.1-rubygem-nokogiri before uninstalling. Accepting not found as a default for zypper_call may not be wanted and cause false negatives/positives.

Further details

Always latest result in this scenario: latest

Related issues 1 (0 open — 1 closed)

Related to openQA Tests (public) - action #34255: [sle] test fails in kdump_and_crash - fail related to ruby2.1-rubygem-nokogiriResolvedmgriessmeier2018-04-04

Actions
Actions
Copy link
 #1

Updated by SLindoMansilla about 7 years ago

  • Related to action #34255: [sle] test fails in kdump_and_crash - fail related to ruby2.1-rubygem-nokogiri added
Actions
Copy link
 #2

Updated by mgriessmeier about 7 years ago

  • Subject changed from [sle][functional][u] test fails in kdump_and_crash - zypper rm ruby2.1-rubygem-nokogiri NOT FOUND to [sle][functional][u][fast][easy] test fails in kdump_and_crash - zypper rm ruby2.1-rubygem-nokogiri NOT FOUND
  • Due date set to 2018-04-24
  • Status changed from New to In Progress
  • Assignee set to mgriessmeier
  • Target version set to Milestone 15

this should be already fixed by https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4770 in https://progress.opensuse.org/issues/34255

PR was merged shortly after the test was triggered.

I will track this ticket and retrigger the test

Actions
Copy link
 #3

Updated by mgriessmeier about 7 years ago

  • Status changed from In Progress to Resolved

restarted test doesn't fail on this issue -> https://openqa.suse.de/tests/1615141#step/kdump_and_crash/19

Actions
Copy link
 #4

Updated by okurz almost 7 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: extra_tests_in_textmode@svirt-xen-hvm
https://openqa.suse.de/tests/1683352

Actions
Copy link
 #5

Updated by okurz almost 7 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: extra_tests_in_textmode@svirt-xen-hvm
https://openqa.suse.de/tests/1707009

Actions
Copy link
 #6

Updated by okurz almost 7 years ago

guys, if you receive a reminder that a test is still labeled with a ticket like this but it's closed please handle it. I don't receive that notification, you do.

Actions
Copy link
 #7

Updated by okurz almost 7 years ago

  • Due date changed from 2018-04-24 to 2018-07-03
  • Status changed from Resolved to Workable
  • Assignee deleted (mgriessmeier)
  • Priority changed from Normal to High
  • Target version changed from Milestone 15 to Milestone 17

please see my comment above.

Actions
Copy link
 #8

Updated by SLindoMansilla almost 7 years ago

  • Status changed from Workable to In Progress
  • Assignee set to SLindoMansilla
Actions
Copy link
 #9

Updated by SLindoMansilla almost 7 years ago

  • Status changed from In Progress to Resolved

The original issue about removing ruby2.1-rubygem-nokogiri was fixed. The current issue is different, see https://bugzilla.suse.com/show_bug.cgi?id=1098926 and https://bugzilla.suse.com/show_bug.cgi?id=1096935

The job is already properly labeled.

Actions
Copy link

Also available in: Atom PDF