action #116299
Updated by JERiveraMoya over 1 year ago
#### Motivation #### Test ## Observation We should investigate why this modules inherited from previous qam team do not stop to waste our time with timeout issues in slower architectures. It fails pretty often, and fix it it if there is time to move them to development group and rethink what to do with them without the need of reviewing them each time an easy fix (or report a bug) Last occurrence: openQA test in scenario sle-15-SP5-Online-aarch64-yast2_cmd@aarch64 fails in [yast_keyboard](https://openqa.suse.de/tests/9417283/modules/yast_keyboard/steps/16) #### Scope #### ## Test suite description Collect all non-stable QAM team has developed some tests using YaST cmd line, which is less costly to execute and maintain. This test module failing sporadically at least for this first alpha builds in SLE-15-SP5. #### Acceptance criteria #### **AC1**: All suite is using those test modules with sporadic failures in test suite `yast2_cmd` are moved to development group for further investigation QA SLE functional. ## Reproducible #### Additional information #### Fails since (at least) Build [9.1](https://openqa.suse.de/tests/9313677) ## Expected result Last good: (unknown) (or more recent) ## Further investigation means, not now, we can create tickets for them later when we analyze how they are build, most likely the problem is they are not only checking YaST-related configuration, but doing things for reals and there might be other squads more interested on details Always latest result in this kind of testing. scenario: [latest](https://openqa.suse.de/tests/latest?arch=aarch64&distri=sle&flavor=Online&machine=aarch64&test=yast2_cmd&version=15-SP5)