Project

General

Profile

action #80746

test fails in await_install - openQA hasn't inherit the comments for incomplete job

Added by leli 8 months ago. Updated 8 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
2020-12-07
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

It is better that openQA inherit the comments for incomplete job automatically, so we do not need to add comments for each incomplete jobs. Thanks.

Ex: https://openqa.nue.suse.com/tests/5132315#step/await_install/185


Related issues

Related to openQA Project - action #45062: Better visualization of incompletes - show module in which incomplete happensResolved2018-12-12

History

#1 Updated by okurz 8 months ago

  • Related to action #45062: Better visualization of incompletes - show module in which incomplete happens added

#2 Updated by okurz 8 months ago

  • Status changed from New to Workable
  • Assignee set to okurz
  • Target version set to Ready

In general the carry-over is also triggered for "incomplete" jobs but what seems to not work anymore is to show the module in which incompletes happen. This will be handled in #45062 . For incompletes I can also recommend another approach which is using the "auto-review" process as described in https://github.com/os-autoinst/scripts/#auto-review---automatically-detect-known-issues-in-openqa-jobs-label-openqa-jobs-with-ticket-references-and-optionally-retrigger

I will try to extend the openQA documentation accordingly.

#3 Updated by okurz 8 months ago

  • Status changed from Workable to Feedback

#4 Updated by okurz 8 months ago

  • Status changed from Feedback to Resolved

PR merged. This improved the documentation.

leli I have updated the documentation to explain that a "carry-over" can only happen if a test module is reported as failing. This works in principle the same for "failed" as well as for "incomplete" jobs. The alternative is "auto-review", also as mentioned in the documentation. The job you referenced is "timeout_exceeded", not "incomplete" per se. You can either bump MAX_JOB_TIME, prevent the timeout with making tests more efficient or abort earlier.

Also available in: Atom PDF