Project

General

Profile

Actions

action #46820

closed

[functional][u][sporadic] test fails in user_defined_snapshot: bootloader missed

Added by dheidler about 5 years ago. Updated over 4 years ago.

Status:
Rejected
Priority:
High
Assignee:
Category:
Spike/Research
Target version:
SUSE QA - Milestone 28
Start date:
2019-01-29
Due date:
% Done:

0%

Estimated time:
42.00 h
Difficulty:

Description

Observation

openQA test in scenario OpenQA::Schema::Result::TestSuites=HASH(0xa9f4aa8) fails in
user_defined_snapshot

Suggestions

  • Figure out failure rate, regroom ticket from there on.

Reproducible

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

Expected result

Last good: 0114 (or more recent)

Further details

Always latest result in this scenario: latest

Actions #1

Updated by dheidler about 5 years ago

  • Subject changed from test fails in user_defined_snapshot: bootloader missed to [functional][u] test fails in user_defined_snapshot: bootloader missed
Actions #2

Updated by okurz about 5 years ago

  • Target version set to Milestone 24
Actions #3

Updated by SLindoMansilla about 5 years ago

happening also on other architectures. We should make statistical investigation and eventually increase the timeout: https://openqa.suse.de/tests/2725751#step/user_defined_snapshot/41

Actions #4

Updated by okurz almost 5 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_on_gnome
https://openqa.suse.de/tests/2846295

Actions #5

Updated by mgriessmeier almost 5 years ago

  • Target version changed from Milestone 24 to Milestone 25
Actions #6

Updated by mgriessmeier almost 5 years ago

  • Subject changed from [functional][u] test fails in user_defined_snapshot: bootloader missed to [functional][u][sporadic] test fails in user_defined_snapshot: bootloader missed
Actions #7

Updated by mgriessmeier almost 5 years ago

  • Priority changed from Normal to High
  • Target version changed from Milestone 25 to Milestone 26

to be groomed

Actions #8

Updated by szarate over 4 years ago

  • Description updated (diff)
  • Category changed from Bugs in existing tests to Spike/Research
  • Status changed from New to Workable
  • Assignee set to szarate
Actions #9

Updated by mgriessmeier over 4 years ago

  • Target version changed from Milestone 26 to Milestone 27
Actions #10

Updated by szarate over 4 years ago

  • Assignee deleted (szarate)
Actions #11

Updated by SLindoMansilla over 4 years ago

  • Estimated time set to 42.00 h
Actions #12

Updated by mgriessmeier over 4 years ago

  • Target version changed from Milestone 27 to Milestone 28
Actions #13

Updated by jorauch over 4 years ago

  • Status changed from Workable to In Progress
  • Assignee set to jorauch

Creating statistics

Actions #14

Updated by jorauch over 4 years ago

  • Status changed from In Progress to Feedback
Actions #15

Updated by jorauch over 4 years ago

Did not happen anymore, suggest to close this

Actions #16

Updated by mgriessmeier over 4 years ago

jorauch wrote:

Did not happen anymore, suggest to close this

you mean the failing testcases in your statistics are different?
at least it looks related to me...
also happened 3days ago on o.s.d: https://openqa.suse.de/tests/3369241

Actions #17

Updated by jorauch over 4 years ago

This is a different error what happens here, they all got the grub

Actions #18

Updated by SLindoMansilla over 4 years ago

I agree with jorauch, the recent failures are https://bugzilla.suse.com/show_bug.cgi?id=980337 or a different bug in the test. It could be that the module user_defined_snapshot is not selecting the right console, since the next module is able to select x11 and continue.

I will leave to jorauch to decide if he prefers to create a new ticket for the current failure and reject this a not reproducible, or continue with this ticket.

Actions #19

Updated by jorauch over 4 years ago

As I can't see the failures from the statistics in production I would reject this and in case of a new failure we open a new ticket
I am not sure what else you could mean with current failure?

Actions #20

Updated by jorauch over 4 years ago

  • Status changed from Feedback to Rejected

Closing this as discussed in Rocketchat with slindomansilla
It is not reproducable anymore

Actions

Also available in: Atom PDF