QA (public) » openQA Project (public) » openQA Tests (public)

Created in OOO Toolchain test suite, scheduled for x86_64 for Tumbleweed and Leap 15.0 (with help of @SLindoMansilla's permissions, requesting mine for second time in factory channel).

wow, did you just add the testsuite to TW and Leap 15.0 without testing? Also, I don't see it in the Leap 15.0 schedule

For Leap 15.0, fails in install test due to pattern devel_basis doesn't work: http://dhcp227/tests/800 (if openSUSE should share the same code base, probably a bug?)
For Tumbleweed succeeded: http://dhcp227/tests/798
PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4084

test suite disabled for Leap 15 on O3

Verification run of test suite on O3: https://openqa.opensuse.org/tests/560613

Changes from PR needed to fully test on Leap 15.

gh#PR/4084 was merged.
Waiting for verification run on OSD

Verified for TW on OSD: https://openqa.opensuse.org/tests/560820

Waiting for Leap 15: https://openqa.opensuse.org/tests/560909

Leap 15 failed in what looks like a product bug about patterns: https://openqa.opensuse.org/tests/560909#step/install/10

I see that the change to products/opensuse/main.pm is a near duplication of the SLE code which I consider suboptimal. I am proposing a change to the main.pm files but I wonder why you did not schedule "kdump_and_crash" for openSUSE. Does it not work for a specific reason? That should be included or at least properly reasoned.

https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4089 for the simplification.

https://bugzilla.opensuse.org/show_bug.cgi?id=1073238
Refactoring the code as you propose does not make it more optimal, it is just nicer. I am wondering why you didn't use another ticket to enhance the main.pm in openSUSE (anyway you didn't mention this ticket in your PR).
Same answer for kdump_and_crash, good that you noticed, but it was not include on purpose, because the test was not yet in openSUSE scheduled, and we can create another ticket to verify that. Also you know that this test is not scheduled always in sle15 and there is a known bug for it, so better put aside for a while.

Bug reopened: testing in my local openQA instance (before scheduling it in O3 or trying to clone with _GROUP_0, which I can't because I don't have API keys in O3) and using latest image and iso, the problem persists: http://dhcp227/tests/819.

Verification in o3 ooo#573267#10 & bug updated bsc#1073238#c7

It is still blocked:

• https://openqa.opensuse.org/tests/latest?test=sergio_toolchain_zypper&distri=opensuse&flavor=DVD&version=15.0&machine=64bit&arch=x86_64#step/install/11
• https://bugzilla.suse.com/show_bug.cgi?id=1073238#c7

If lnussel doesn't answer in https://bugzilla.suse.com/show_bug.cgi?id=1073238#c7 before the planning, move to next sprint.

Not quite sure what you expect from lnussel to answer. It seems there is no "toolchain_zypper" testsuite enabled for openSUSE Leap 15.0 so you can not that easily check if it works by now. One would need to trigger a test manually based on customized parameters.

Waiting: http://copland.arch.suse.de/tests/874

Test soft-failed.

Verifying on O3. Waiting for: https://openqa.opensuse.org/tests/610701