Project

General

Profile

action #63451

Improve openqa-monitor-incompletes and openqa-label-known-issues to not report about incompletes with clone

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

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

0%

Estimated time:
Difficulty:

Description

Observation

On Thursday, 13 February 2020 22.35.33 CET Grafana wrote:

[Alerting] New incompletes alert

Metric name

Value

New incompletes

27.000

keep in minds. I bumped the alert threshold so that only if 25 new incompletes occur within one reporting period, that is just 10 seconds (!). I checked 2 out of many jobs and found the same reason:
"Reason: associated worker re-connected but abandoned the job"

The good thing is that they have all been automatically cloned.

Suggestions

I guess we need just one more change to the scripts in https://github.com/os-autoinst/scripts/ :

  1. ignore incompletes that have a clone

Who wants to give it a shot? :)


Related issues

Related to openQA Project - action #69178: workaround for #64776 using https://github.com/os-autoinst/scripts/blob/master/openqa-label-known-issuesResolved2020-07-212020-07-31

History

#1 Updated by okurz over 1 year ago

  • Target version set to Ready

#2 Updated by okurz about 1 year ago

  • Status changed from New to Workable

#3 Updated by okurz about 1 year ago

  • Related to action #69178: workaround for #64776 using https://github.com/os-autoinst/scripts/blob/master/openqa-label-known-issues added

#4 Updated by okurz about 1 year ago

  • Subject changed from Improve openqa-monitor-incompletes and openqa-label-known-issues to not report about incompletes with clone / no complain about no logs when there is "reason" to Improve openqa-monitor-incompletes and openqa-label-known-issues to not report about incompletes with clone
  • Description updated (diff)

#5 Updated by okurz about 1 year ago

  • Status changed from Workable to Rejected
  • Assignee set to okurz

I am thinking about the following use-case: A human reviewer is grumpily retriggering an incomplete every day so there is a clone in this case but that person never reports the issue so we would not catch these problems. Rather than skipping the incompletes in openqa-monitor-incompletes we could skip over trying to clone the incompletes in openqa-label-known-issues but the API call is a no-op anyway so let's just not care.

#6 Updated by okurz about 1 year ago

  • Status changed from Rejected to Resolved
  • Assignee changed from okurz to cdywan

Actually cdywan and me discussed this and only then realized what the proper use case is so the honor goes to him.

Also available in: Atom PDF