openQA Project - coordination #39719: [saga][epic] Detection of "known failures" for stable tests, easy test results review and easy tracking of known issues
Most of SUSE openQA contributors have selected to use YAML schedule files per openQA scenario in comparison to previously using a shared schedule definition where differences would all be noted down explicitly. This obviously over time introduced the problem of differing coverage which was made more significant with #54839 which of course helped to mitigate short-term pain because teams "felt" as if they would step less on each other's toes. But now the pressure grows to keep the schedules aligned where it makes sense.
- AC1: static checks in os-autoinst-distri-opensuse ensure that schedules do not differ further unnecessarily
- AC2: Differences in schedules can be accepted with commented reasons
#3 Updated by okurz about 2 months ago
- Subject changed from [tools] os-autoinst-distri-opensuse YAML schedule file comparison to [qe-core] os-autoinst-distri-opensuse YAML schedule file comparison
tjyrinki_suse the SUSE QE Tools team does not own or commonly contribute to "os-autoinst-distri-opensuse". In my understanding still as defined in the SUSE QE teams restructuring ultimately QE-Core owns os-autoinst-distri-opensuse, this is your baby :) So you (your team) need to drive that. Of course SUSE QE Tools team members are happy to help on demand, e.g. for technical feasibilities, specific YAML support, etc.