Project

General

Profile

Actions

coordination #95857

open

[epic] QAM incident tests: Fix "next & previous", latest results and label carry-over

Added by okurz almost 3 years ago. Updated over 2 years ago.

Status:
Workable
Priority:
Low
Assignee:
-
Target version:
Start date:
2021-07-22
Due date:
% Done:

0%

Estimated time:

Description

Motivation

For QAM incident tests we should consider using flavor rather than build to encode incident+test to ensure that

  • "Next & previous" results only show results for the very same incident, not all different kind of packages
  • openQA can resolve the real "latest" result per incident on /tests/overview, e.g. to make reports on https://openqa.io.suse.de/openqa-review/ more useful for incident tests as well
  • label carry over works for repeated failures within the same incident

Acceptance criteria

Suggestions

  • Without changing the build variable we could try to just add the package (maybe also the incident number) to flavor. Likely this needs to be done in qa-maintenance/openQABot (or the metadata project)
  • To avoid confusion, this is about links that are generated in a previous part but no the webui "next & prev"
  • One example: https://openqa.suse.de/tests/6511087#next_previous shows how we treat all different kind of incidents for different packages as the "same scenario" because flavor is always "Server-DVD-Incidents" here, only build differs. What we could do is change the flavor in this case for build ":20484:spice-vdagent" to "Server-DVD-Incidents:20484:spice-vdagent" but if we set the different flavor then we likely don't trigger any tests anymore :( Should we remove anything after a special token like ":" and don't consider for scheduling? Maye introduce another optional, custom "external reference" field? or "flavor tags"? :) As alternative maybe use a custom version suffix and ensure that the "fallback version product pattern matching" still works, using the asterisk "*" in a version field.

Related issues 2 (1 open1 closed)

Related to openQA Tests - action #92921: [tools][spike] Can we change or display job group structure for maintenance job groups to have one job group per team like for product validation and maybe specific products and versions below size:MResolvedmgrifalconi2021-05-21

Actions
Related to QA - coordination #153928: [epic] Ideas from SUSE QE Tools workshop 2024-01-19 Filter openQA todo-jobs on /tests belonging to groups, review teams, etcNew

Actions
Actions #1

Updated by okurz almost 3 years ago

  • Related to action #92921: [tools][spike] Can we change or display job group structure for maintenance job groups to have one job group per team like for product validation and maybe specific products and versions below size:M added
Actions #2

Updated by okurz almost 3 years ago

  • Description updated (diff)
Actions #3

Updated by ilausuch almost 3 years ago

  • Subject changed from QAM incident tests: Fix "next & previous", latest results and label carry-over to QAM incident tests: Fix "next & previous", latest results and label carry-over size:M
  • Status changed from New to Workable
Actions #4

Updated by ilausuch almost 3 years ago

  • Subject changed from QAM incident tests: Fix "next & previous", latest results and label carry-over size:M to QAM incident tests: Fix "next & previous", latest results and label carry-over
Actions #5

Updated by ilausuch almost 3 years ago

  • Description updated (diff)
Actions #6

Updated by okurz almost 3 years ago

  • Description updated (diff)
  • Status changed from Workable to New
Actions #7

Updated by okurz almost 3 years ago

  • Description updated (diff)
  • Priority changed from Normal to Low

maybe worth to discuss the general idea and concept e.g. during a SUSE QE Tools workshop. TODO make it an epic and create specific subtask to present the concept and gather feedback, e.g. in workshop

Actions #8

Updated by okurz almost 3 years ago

  • Tracker changed from action to coordination
  • Subject changed from QAM incident tests: Fix "next & previous", latest results and label carry-over to [epic] QAM incident tests: Fix "next & previous", latest results and label carry-over
Actions #9

Updated by okurz almost 3 years ago

  • Status changed from New to Workable

In the weekly estimation meeting we decided that for an epic it's actually "Workable" because we don't need to estimate the epic itself and the next task is simply to refine and create subtasks

Actions #10

Updated by okurz almost 3 years ago

  • Description updated (diff)
Actions #11

Updated by okurz over 2 years ago

  • Target version changed from Ready to future

Apparently not really motivating to the team to be picked up. We can re-evaluate at a later time. Removing from current backlog due to backlog constraints

Actions #12

Updated by okurz 5 months ago

  • Related to coordination #153928: [epic] Ideas from SUSE QE Tools workshop 2024-01-19 Filter openQA todo-jobs on /tests belonging to groups, review teams, etc added
Actions

Also available in: Atom PDF