Project

General

Profile

Actions

action #119887

closed

coordination #119836: [epic] Convert YAML schedules for YaST to be based on YAML default files

Modify existing default yaml file for x86_64 64bit and adapt test suites to use it in YaST group

Added by JERiveraMoya over 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
Start date:
2022-11-04
Due date:
% Done:

0%

Estimated time:

Description

Observation

Current default file called default.yaml represents x86_64 64bit, but we don't need the full name, we can keep as default.yaml.
In this ticket we will update this file to make it work with all the test suites for x86_64 64 bit, excluding other flavors of x86_64.

This is the list of jobs:
https://openqa.suse.de/tests/overview?arch=&flavor=&machine=64bit&test=&modules=&module_re=&distri=sle&version=15-SP5&build=32.1&groupid=129#
Filter by 64bit to get the list of modules for latest build in case the link got outdated.

Acceptance criteria

AC1: Adapt default yaml file for x86_64 64bit to work with all the test suite listed above
AC2: Modify only schedules for x86_64 64 bit to make them work with new created default

Suggestions

  • If one schedule is used for several architecture/backend, rather than modify it, we can create a new schedule file for now using keys instead of list of modules.
  • Take inspiration from other tasks done in Epic where this task belongs.
  • For now there is not much thought about how the solution would work for test suites after installation, so let's focus on installation and consider the rest of test suite, if it feasible we can try out, otherwise file a ticket for them.
Actions #1

Updated by JERiveraMoya over 1 year ago

  • Tags set to qe-yast-refinement
Actions #2

Updated by JERiveraMoya over 1 year ago

  • Tags deleted (qe-yast-refinement)
Actions #3

Updated by hjluo over 1 year ago

  • Status changed from Workable to In Progress
  • Assignee set to hjluo
Actions #5

Updated by JERiveraMoya over 1 year ago

  • Status changed from In Progress to Resolved
Actions #8

Updated by JERiveraMoya about 1 year ago

  • Status changed from Resolved to In Progress

missed to re-open the ticket once we found issues.

Actions #9

Updated by JERiveraMoya about 1 year ago

  • Status changed from In Progress to Resolved

let's keep an eye on failures in new build and send quick PR.
We can resolve it.

Actions #10

Updated by hjluo about 1 year ago

  • Status changed from Resolved to In Progress
Actions #11

Updated by hjluo about 1 year ago

  • Status changed from In Progress to Resolved

now all setting issues were fixed with quick MRs. mark it as resolved.

Actions

Also available in: Atom PDF