action #92566
closed[qe-sap][qem][SAP]test fails in Sysctl
100%
Description
Observation¶
Seems like the test range should be updated. Conversation here https://chat.suse.de/channel/qem-openqa-review?msg=MxroYK9HwdQGQEexE
openQA test in scenario sle-15-SP1-SAP-DVD-Updates-x86_64-sles4sap_robot_fw@64bit-2gbram fails in
Sysctl
Test suite description¶
The base test suite is used for job templates defined in YAML documents. It has no settings of its own.
Reproducible¶
Fails since (at least) Build 20210511-1
Expected result¶
Last good: 20210510-2 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by dzedro over 3 years ago
- Priority changed from Normal to High
Julien is working on another project for few months, this won't be solved by anybody else
adding soft fail https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/12593
Updated by jadamek over 3 years ago
dzedro wrote:
Julien is working on another project for few months, this won't be solved by anybody else
adding soft fail https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/12593
Yes, I'm in a exchange process, someone else than me can fix it for sure, please contact #qa-sap-ha.
Updated by okurz over 3 years ago
This ticket was set to "High" priority but was not updated within the SLO period for "High" tickets (30 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives . Please consider picking up this ticket within the next 30 days or just set the ticket to the next lower priority of "Normal" (SLO: updated within 365 days). This update was done as agreed within the SUSE QE Sync call 2021-09-01
Updated by okurz over 3 years ago
- Subject changed from [qem][SAP]test fails in Sysctl to [qe-sap][qem][SAP]test fails in Sysctl
Using keyword "qe-sap" as verified by jmichel in weekly QE sync 2021-09-15
Updated by jadamek over 3 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 50
I checked the last fifteen tests and I can not see this issue anymore, the related softail is not triggered.
Unfortunately, I can't see what was the returned value as the job history has gone.
Let me remove the softail and monitor the test before closing this ticket.
Updated by jadamek over 3 years ago
Ok I got the info from the commit message:
The returned value was 91284 and we expect something in the range '80000:91000'
Let's remove the softfail before increasing the range.
Updated by jadamek over 3 years ago
- Status changed from In Progress to Feedback
- Priority changed from High to Normal
- % Done changed from 50 to 90
Updated by jadamek about 3 years ago
- Status changed from Feedback to Resolved
- % Done changed from 90 to 100
The issue no longer happens, let's resolve this ticket for now.