Project

General

Profile

action #118360

[qem][security] test fails in syscall_thrasher - command './thrash' timed out

Added by vsvecova 4 months ago. Updated 2 months ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2022-10-12
Due date:
% Done:

100%

Estimated time:
Difficulty:
Tags:

Description

Observation

command './thrash' timed out

From investigation jobs:
cc_atsec:investigate:bisect_without_26341: https://openqa.suse.de/t9715436 - green
Plain retry jobs failing.

openQA test in scenario sle-15-SP3-Server-DVD-Updates-x86_64-cc_atsec@64bit fails in
syscall_thrasher

Test suite description

Testsuite maintained at https://gitlab.suse.de/qe-security/osd-sle15-security.

Reproducible

Fails since (at least) Build 20221011-1

Expected result

Last good: 20221010-1 (or more recent)

Further details

Always latest result in this scenario: latest

History

#1 Updated by tjyrinki_suse 4 months ago

  • Subject changed from [qem][qe-security] test fails in syscall_thrasher - command './thrash' timed out to [qem][security] test fails in syscall_thrasher - command './thrash' timed out

#2 Updated by pstivanin 4 months ago

  • Status changed from New to In Progress
  • Assignee set to pstivanin

#3 Updated by pstivanin 4 months ago

  • % Done changed from 0 to 100

In 15-SP4, we've added more ram and cpus and this made the test stable.
With https://gitlab.suse.de/qe-security/osd-sle15-security/-/merge_requests/17 we are adding the same resources also to 15-SP3.

#4 Updated by pstivanin 4 months ago

we will keep this open for a few days, to see if the above change was enough to stabilize the test.

#5 Updated by pstivanin 4 months ago

test is running stable so far. Let's keep this open until Monday.

#7 Updated by pstivanin 4 months ago

  • Status changed from In Progress to Resolved

#8 Updated by vsvecova 3 months ago

Hello Paolo, the test has still been failing a lot: https://openqa.suse.de/tests/9963111#next_previous Especially in the latest days, but not only.

Should we reopen this ticket? The issue seems to be the same. Or let me know if you prefer a new one instead.

#9 Updated by vsvecova 3 months ago

  • Status changed from Resolved to In Progress

Reopening as agreed

#10 Updated by punkioudi 3 months ago

  • Assignee changed from pstivanin to punkioudi
  • Priority changed from Normal to High

Assigning myself to this ticket, as Paolo is on FTO.

#12 Updated by punkioudi 2 months ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF