Project

General

Profile

Actions

action #55748

closed

[sle][security][sle12sp5][s390x] Test will stop running while the previous test fail in s390x

Added by bchou over 4 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2019-08-20
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observe that the s390x testing worker will be stopped running if fail. But it will keep running in x86_64.

in 390x (stop running if fail)
https://openqa.suse.de/tests/3264068

in x86_64 (keep running if fail)
https://openqa.suse.de/tests/3263109

Actions #1

Updated by bchou over 4 years ago

Hello Oliver@okurz,

I Observe the issue is also happening in other job group and will this be the s390x vm backend problem? And it will not workaround it currently?

Thanks a lot.

Actions #2

Updated by okurz over 4 years ago

Is this a question about continuing a test even though single modules fail? This feature is not supported for the s390x kvm backend so any failure will also stop the job execution.

Actions #3

Updated by bchou over 4 years ago

Hi Oliver,

Thanks for your feedback,

Is there any way to work around this, or we have to change the testing sequence?

Actions #4

Updated by bchou over 4 years ago

Oliver mentioned:

We can either implement support in the backend, because technically it's possible, or you make sure the test module does not fail, e.g. track the known issue with a soft failure, or you change the testing sequence or you split the test scenario into multiple independent ones.

Actions #5

Updated by bchou over 4 years ago

bchou wrote:

Oliver mentioned:

We can either implement support in the backend, because technically it's possible, or make sure the test module does not fail, e.g. track the known issue with a soft failure, or change the testing sequence or split the test scenario into multiple independent ones.

Actions #6

Updated by bchou over 4 years ago

  • Status changed from New to Closed

The issue is a common s390x backend problem,

We can wait for the implementation support in the backend later. Thanks.

Actions

Also available in: Atom PDF