Project

General

Profile

action #115184

[qe-core] Prepare for ALP - Move ALP test scheduling to YAML

Added by szarate about 2 months ago. Updated 4 days ago.

Status:
Feedback
Priority:
Normal
Assignee:
Category:
New test
Target version:
Start date:
2022-08-10
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Since we're starting with a brand new product, and it's still in development, we can use the opportunity to shy away from main.pm for scheduling tests avoiding the behemoth that we have for other products for both, SUSE and openSUSE.

As with #115181 we will need to coordinate with other contributors, but that doesn't stop us from coming up with default schedules, and a template for tests that boot from an already installed image in the future

Acceptance criteria

AC1: Pull request with a PoC/RFC for the change is created (not necessarily merged)


Related issues

Copied from openQA Tests - action #115181: [qe-core] Prepare for ALP - Enablement of ALP for QE-CoreFeedback

History

#1 Updated by szarate about 2 months ago

  • Copied from action #115181: [qe-core] Prepare for ALP - Enablement of ALP for QE-Core added

#2 Updated by RBrownSUSE about 1 month ago

I don't hold any huge objection to this, but given ALP is a derivative of both Tumbleweed and MicroOS, the only question is how do we expect ALP to keep its test coverage aligned with its upstream if we do this?

Both MicroOS and Tumbleweed use main.pms, and whatever coverage is added to ALP would ideally exist in one of those two domains before

#3 Updated by jlausuch 27 days ago

Yes, I agree with @RBrownSUSE here.
I would actually go even further and create a common main_microos.pm (or whatever name) for ALP, MicroOS, Leap Micro and SLE Micro, since most of the tests/schedules will be shared.

#4 Updated by szarate 27 days ago

Carrying over to next sprint

#5 Updated by szarate 27 days ago

  • Sprint changed from QE-Core: August Sprint (Aug 03 - Aug 31) to QE-Core: September Sprint (Aug 31 - Sep 28)

#6 Updated by apappas 18 days ago

  • Status changed from Workable to Feedback
  • Assignee set to szarate

This ticket is unclear. There have been discussions about extending/rewording/clarifying it. So I am setting it to feedback.

#7 Updated by szarate 7 days ago

Both MicroOS and Tumbleweed use main.pms, and whatever coverage is added to ALP would ideally exist in one of those two domains before
the only question is how do we expect ALP to keep its test coverage aligned with its upstream if we do this?

Hmmm, we need to replan this, to be able to guarantee that this will stay true, without overloading O3.

I would actually go even further and create a common main_microos.pm (or whatever name) for ALP, MicroOS, Leap Micro and SLE Micro, since most of the tests/schedules will be shared.

@Jose, you mean that main_microos.pm is a single file, that exists for all of the 3 distributions?

#8 Updated by szarate 7 days ago

Gonna move it out of the sprint, for now we're using YAML schedule for new testsuites, all of those test modules enabled run already on TW.

#9 Updated by szarate 7 days ago

  • Sprint deleted (QE-Core: September Sprint (Aug 31 - Sep 28))
  • Target version deleted (QE-Core: Ready)

#10 Updated by jlausuch 7 days ago

  • Target version set to QE-Core: Ready

Maybe we can have a meeting where I go through the code to see the benefit of using a specific and separated main_xyz.pm for the products:

  • MicroOS
  • SLE Micro
  • Leap Micro
  • ALP

#11 Updated by okurz 4 days ago

szarate wrote:

Hmmm, we need to replan this, to be able to guarantee that this will stay true, without overloading O3.

In case you are concerned regarding hardware ressources rest assured that we have enough headroom. And in case we do run into limits I am convinced we will be able to improve.

Also available in: Atom PDF