Project

General

Profile

Actions
Copy link

action #19386

closed

[opensuse][leap]test fails in kdump_and_crash with core dump in configuration ui -> product issue?

Added by lnussel almost 7 years ago. Updated almost 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
okurz
Category:
Bugs in existing tests
Target version:
-
Start date:
2017-05-26
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario opensuse-42.3-DVD-x86_64-extra_tests_in_textmode@64bit fails in
kdump_and_crash

Reproducible

Fails since (at least) Build 0163

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest

Related issues 1 (0 open — 1 closed)

Related to openQA Tests - action #16436: [sles][functional] test fails in crash with timeout on running scriptResolved2017-02-03

Actions
Actions
Copy link
 #1

Updated by okurz almost 7 years ago

  • Status changed from New to Feedback
  • Assignee set to okurz

https://openqa.opensuse.org/tests/408418#step/kdump_and_crash/18 shows core dumped. That's hardly a test issue. Is it?

Actions
Copy link
 #2

Updated by okurz almost 7 years ago

  • Subject changed from test fails in kdump_and_crash to [opensuse][leap]test fails in kdump_and_crash with core dump in configuration ui -> product issue?
Actions
Copy link
 #3

Updated by okurz almost 7 years ago

  • Related to action #16436: [sles][functional] test fails in crash with timeout on running script added
Actions
Copy link
 #4

Updated by Anonymous almost 7 years ago

I had a look of the instlog, and it seems to me that the test falls into loop because it can't find the matching needle yast2_console-finished from activate_kdump function: until (match_has_tag('yast2_console-finished') . We can either check for the needle in the repo, or change the function into simply sending keys without checking for the needle.

Actions
Copy link
 #5

Updated by osukup almost 7 years ago

no this looks like real product problem , yast should not segfault with end of work

Actions
Copy link
 #6

Updated by okurz almost 7 years ago

  • Assignee changed from okurz to lnussel

yes, please read the subject line of this ticket carefully. Also http://openqa.opensuse.org/tests/408418/modules/kdump_and_crash/steps/18 looks pretty obvious: There is an error message with segfault.

@lnussel: can you comment why you think this is not a product issue? Or did you overlook the segfault?

Actions
Copy link
 #7

Updated by lnussel almost 7 years ago

  • Assignee changed from lnussel to okurz

It is likely a yast problem but since the test doesn't collect any log files or core dumps after it failed I can hardly file a bug myself with the information available. So QA has to reproduce this.

Actions
Copy link
 #8

Updated by okurz almost 7 years ago

  • Status changed from Feedback to Resolved

Logs are available now (that should be my change about using the log-console). I created a product bug with the corresponding log info now: https://bugzilla.opensuse.org/show_bug.cgi?id=1043389

Actions
Copy link

Also available in: Atom PDF