Project

General

Profile

Actions
Copy link

action #36580

closed

[functional][y][medium] stress test fails: undefined HASH value in ctcs2_to_junit.pm

Added by nicksinger almost 6 years ago. Updated almost 6 years ago.

Status:
Resolved
Priority:
High
Assignee:
riafarov
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 17
Start date:
2018-05-28
Due date:
2018-06-19
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

all openQA test in the scenario sle-12-SP4-Server-DVD fail while executing the different stress tests. E.g.:
execute_test_run

With the error message:

# Test died: Can't use an undefined value as a HASH reference at /var/lib/openqa/cache/tests/sle/lib/ctcs2_to_junit.pm line 42.

Reproducible

Fails since Build 0246 (current job)

Further details

Last commit on lib/ctcs2_to_junit.pm was 7e5c3196b2e6052ad02411c4c0d399c2d2bc7db6 at Tue Apr 24 17:27:00 2018 +0800. The last successful run was at 18th of May 2018. So maybe it is not directly related to the last change in that file.

Actions
Copy link
 #1

Updated by nicksinger almost 6 years ago

  • Description updated (diff)
Actions
Copy link
 #2

Updated by mgriessmeier almost 6 years ago

  • Due date changed from 2018-06-05 to 2018-06-19
Actions
Copy link
 #3

Updated by mgriessmeier almost 6 years ago

  • Subject changed from [functional][fast] stress test fails: undefined HASH value in ctcs2_to_junit.pm to [functional][y] stress test fails: undefined HASH value in ctcs2_to_junit.pm
Actions
Copy link
 #4

Updated by riafarov almost 6 years ago

  • Assignee set to riafarov
Actions
Copy link
 #6

Updated by mgriessmeier almost 6 years ago

  • Subject changed from [functional][y] stress test fails: undefined HASH value in ctcs2_to_junit.pm to [functional][y][medium] stress test fails: undefined HASH value in ctcs2_to_junit.pm
  • Status changed from Workable to Feedback
Actions
Copy link
 #7

Updated by okurz almost 6 years ago

merged, SLE12SP4 did not show stress test failures like the original one so I do not know what to retrigger here but a s390x zkvm test failed: https://openqa.suse.de/tests/1748913 Symptoms look different but I will retrigger nevertheless and we can use this as verification when it did not fail -> https://openqa.suse.de/tests/1752453#settings

Actions
Copy link
 #8

Updated by riafarov almost 6 years ago

@okurz, original issue was on ppc64le. I suggest to resolve it as of now and aim investigation once we see these failures related to script_output again. WDYT?

Actions
Copy link
 #9

Updated by okurz almost 6 years ago

  • Status changed from Feedback to Resolved
  • Target version set to Milestone 17

My point was to find at least a verification run on osd that shows that we have not horribly broken everything :) So any non-ppc64le is good enough. The s390x failed in before so was no good but I assume any stress test suffices. https://openqa.suse.de/tests/1752743 is a QAM test that just passed 3 minutes ago so I assume we are good.

Actions
Copy link
 #10

Updated by okurz almost 6 years ago

  • Target version changed from Milestone 17 to Milestone 17
Actions
Copy link

Also available in: Atom PDF