Project

General

Profile

action #106909

coordination #91646: [saga][epic] SUSE Maintenance QA workflows with fully automated testing, approval and release

coordination #98457: [epic] Handle openqa-review reminder comments on very old jobs better

[openqa-review] reminder comments point to specific openQA test details steps or openQA comments size:M

Added by okurz 5 months ago. Updated 3 months ago.

Status:
Resolved
Priority:
Low
Assignee:
Target version:
Start date:
2022-02-16
Due date:
% Done:

0%

Estimated time:

Description

Motivation

As a ticket reader encountering openqa-review reminder comments I want to know which specific openQA test details step or needle triggered a reminder comment so that I can better fix the issue and prevent the reminder

Acceptance criteria

  • AC1: The openqa-review reminder comments point to the specific openQA test detail step or comment that triggered a reminder comment

Suggestions

  • Extend the reminder comments to state where exactly the ticket reference comes from, at best point the step detail in openQA
  • For reminder comments triggered by openQA comments (mostly failed jobs, not softfailed) inform about that specifically as well
  • Alternatives: Specific code location or the workaround needle in the git repo that references a ticket. For reference, the autoinst-log.txt has a line [2022-02-08T11:34:07.525532+01:00] [debug] needle 'generic-desktop-test-20220206' is a workaround. The reason is bsc#123456

History

#1 Updated by okurz 5 months ago

  • Priority changed from Normal to Low

#2 Updated by cdywan 4 months ago

  • Subject changed from [openqa-review] reminder comments point to specific openQA test details steps or openQA comments to [openqa-review] reminder comments point to specific openQA test details steps or openQA comments size:M
  • Description updated (diff)
  • Status changed from New to Workable

#3 Updated by jbaier_cz 3 months ago

  • Assignee set to jbaier_cz

#4 Updated by jbaier_cz 3 months ago

  • Status changed from Workable to In Progress

#5 Updated by jbaier_cz 3 months ago

I drafted a PR which adds logic to include steps from failures. Now, I am investigating another mentioned options (needles, comments).

#6 Updated by jbaier_cz 3 months ago

  • Status changed from In Progress to Feedback

The PR is now merged, now we need to wait for results and evaluate.

#8 Updated by jbaier_cz 3 months ago

  • Status changed from Feedback to Resolved

And also one in bugzilla: https://bugzilla.suse.com/show_bug.cgi?id=1194208#c11

I assume the feature is working.

Also available in: Atom PDF