action #57101

action #47003: [epic][functional][u][ppc64le] test runs into MAX_JOB_TIME - split extra_tests_in_textmode

action #57290: [functional][u] Move module specific test modules from extra_tests_* scenarios to its respective scenario

[qam][functional][u] test fails in gdb - Missing module development tools

Added by SLindoMansilla 7 months ago. Updated 16 days ago.

Status:BlockedStart date:19/09/2019
Priority:HighDue date:
Assignee:SLindoMansilla% Done:

0%

Category:Bugs in existing tests
Target version:-
Difficulty:
Duration:

Description

Observation

openQA test in scenario sle-15-SP2-Installer-DVD-x86_64-extra_tests_in_textmode@64bit fails in
gdb

Reproducible

Fails since (at least) Build 20.3

Expected result

Last good: Not known

Further details

Always latest result in this scenario: latest


Related issues

Related to openQA Tests - action #57227: [sle][functional][u][sporadic] ldapadd failure, test_abor... Rejected 23/09/2019

History

#1 Updated by SLindoMansilla 7 months ago

Assigned to module maintainer ;)

#2 Updated by apappas 7 months ago

  1. Did something change with the SLE15SP2 groups since the test runs fine on SLE15SP1
  2. What do you thing is the best place to put it?

#3 Updated by SLindoMansilla 7 months ago

  • Subject changed from [qam] test fails in gdb - Test module gdb wrongly scheduled on scenario without development tools module enabled to [qam] test fails in gdb - Missing module development tools

apappas wrote:

  1. Did something change with the SLE15SP2 groups since the test runs fine on SLE15SP1
  2. What do you thing is the best place to put it?

ah, sorry, it seems that on that maintenance scenario you already add the module. So, the problem was that this module was new on our scenario and I thought it was wrongly scheduled. It just need adjustments.
In the scenario that is failing, the system is registered, but we only add modules when needed and remove them after the test module finishes.

What do you think about my proposal?: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/8493

#4 Updated by SLindoMansilla 6 months ago

I think this is starting to be over engineered: http://openqa.slindomansilla-vm.qa.suse.de/tests/1644#step/gdb/67
Caused by this proposal: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/8493

It fails to deactivate the module due to dependencies. Which brings me back to my initial thought. This module gdb should not be added in that scenario. I can think on an scenario that tests SDK. I haven't found any specific test suite for that, but, I found the create_hdd_minimal_base+sdk.
As we already wanted to split the extra_tests_* nightmare, what do you think about starting a split by SLE modules?
So, I would create a testsuite extra_tests_for_sdk.

#5 Updated by SLindoMansilla 6 months ago

  • Subject changed from [qam] test fails in gdb - Missing module development tools to [qam][functional][u] test fails in gdb - Missing module development tools
  • Assignee changed from apappas to SLindoMansilla

Found proper scenario for that test: sle-12-SP5-Server-DVD-x86_64-sdk@64bit

#6 Updated by SLindoMansilla 6 months ago

Created new test suite extra_tests_sdk

BOOT_HDD_IMAGE=1
DESKTOP=textmode
EXTRATEST=sdk
HDD_1=SLES-%VERSION%-%ARCH%-%BUILD%@%MACHINE%-minimal_with_sdk%BUILD_SDK%_installed_withhome.qcow2
START_AFTER_TEST=create_hdd_minimal_base+sdk_withhome
UEFI_PFLASH_VARS=SLES-%VERSION%-%ARCH%-%BUILD%@%MACHINE%-minimal_with_sdk%BUILD_SDK%_installed_withhome-uefi-vars.qcow2

Enabled for Test Development: SLE 15 on 64bit machine

#7 Updated by SLindoMansilla 6 months ago


Verification run: https://openqa.suse.de/tests/3431306#next_previous

Test extra_tests_sdk moved from Test Development: SLE 15 (sle-15-SP2-Installer-DVD) to Functional: sle-15-SP2-Installer-DVD

Wrong, because the PR was not yet merged. Sorry for the noise.

#10 Updated by SLindoMansilla 6 months ago

  • Related to action #57227: [sle][functional][u][sporadic] ldapadd failure, test_abort 'Failed to prepare LDAP server' added

#11 Updated by okurz 6 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: extra_tests_in_textmode
https://openqa.suse.de/tests/3463058

To prevent further reminder comments one of the following options should be followed:
1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
2. The openQA job group is moved to "Released"
3. The label in the openQA scenario is removed

#12 Updated by SLindoMansilla 5 months ago

  • Related to action #57290: [functional][u] Move module specific test modules from extra_tests_* scenarios to its respective scenario added

#13 Updated by okurz 5 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: extra_tests_in_textmode
https://openqa.suse.de/tests/3547216

To prevent further reminder comments one of the following options should be followed:
1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
2. The openQA job group is moved to "Released"
3. The label in the openQA scenario is removed

#14 Updated by szarate 5 months ago

  • Status changed from New to Blocked

see #57290

#15 Updated by okurz 4 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: extra_tests_in_textmode
https://openqa.suse.de/tests/3641351

To prevent further reminder comments one of the following options should be followed:
1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
2. The openQA job group is moved to "Released"
3. The label in the openQA scenario is removed

#16 Updated by SLindoMansilla 4 months ago

  • Status changed from Blocked to In Progress

#57290 is waiting for verification run. It is time to continue on this.

#17 Updated by SLindoMansilla 4 months ago

  • Related to deleted (action #57290: [functional][u] Move module specific test modules from extra_tests_* scenarios to its respective scenario)

#18 Updated by SLindoMansilla 4 months ago

  • Parent task set to #57290

#19 Updated by SLindoMansilla 4 months ago

MR for dev job group: https://gitlab.suse.de/qsf-u/qa-sle-functional-userspace/merge_requests/15/diffs
It doesn't scale to wait for approval and review on your own job group

#20 Updated by SLindoMansilla 4 months ago

Test suite updated.

extra_tests_in_textmode_sdk

BOOT_HDD_IMAGE=1
DESKTOP=textmode
EXTRATEST=sdk
HDD_1=SLES-%VERSION%-%ARCH%-%BUILD%@%MACHINE%-minimal_with_sdk%BUILD_SDK%_installed.qcow2
START_AFTER_TEST=create_hdd_minimal_base+sdk
UEFI_PFLASH_VARS=SLES-%VERSION%-%ARCH%-%BUILD%@%MACHINE%-minimal_with_sdk%BUILD_SDK%_installed-uefi-vars.qcow2

#21 Updated by okurz 3 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: extra_tests_in_textmode
https://openqa.suse.de/tests/3715782

To prevent further reminder comments one of the following options should be followed:
1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
2. The openQA job group is moved to "Released"
3. The label in the openQA scenario is removed

#22 Updated by okurz 3 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: extra_tests_in_textmode
https://openqa.suse.de/tests/3767851

To prevent further reminder comments one of the following options should be followed:
1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
2. The openQA job group is moved to "Released"
3. The label in the openQA scenario is removed

#23 Updated by okurz 2 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: extra_tests_in_textmode
https://openqa.suse.de/tests/3822751

To prevent further reminder comments one of the following options should be followed:
1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
2. The openQA job group is moved to "Released"
3. The label in the openQA scenario is removed

#24 Updated by okurz 2 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: extra_tests_in_textmode
https://openqa.suse.de/tests/3822751

To prevent further reminder comments one of the following options should be followed:
1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
2. The openQA job group is moved to "Released"
3. The label in the openQA scenario is removed

#25 Updated by okurz about 1 month ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: extra_tests_in_textmode@svirt-xen-hvm
https://openqa.suse.de/tests/3885556

To prevent further reminder comments one of the following options should be followed:
1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
2. The openQA job group is moved to "Released"
3. The label in the openQA scenario is removed

#26 Updated by SLindoMansilla about 1 month ago

  • Status changed from In Progress to Blocked

It is actually being worked on: #57290

#27 Updated by okurz 30 days ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: extra_tests_in_textmode
https://openqa.suse.de/tests/3957200

To prevent further reminder comments one of the following options should be followed:
1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
2. The openQA job group is moved to "Released"
3. The label in the openQA scenario is removed

#28 Updated by mgriessmeier 18 days ago

  • Priority changed from Normal to Urgent

as discussed with RMs, we want to reduce failing test cases and this looks fairly easy - therefore bumping priority

#29 Updated by SLindoMansilla 16 days ago

  • Priority changed from Urgent to High

Also available in: Atom PDF