Project

General

Profile

action #105019

coordination #105142: [epic] More statistics in job results

Make the number of previous restarts of a job more discoverable size:M

Added by coolo 4 months ago. Updated 4 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
2022-01-18
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

https://openqa.suse.de/tests/7991880#next_previous shows a test failure retriggered 10 times in 12 days, but you really have to search for that. The job page already includes the information it was cloned, but not that that job already was cloned X times.
And I think it should, because for a test failure that looks randomly failing, it makes a huge difference if it was restarted 0, 1 or 10 times.

Acceptance criteria

  • AC1: An unusally high number of restarts is visible in the job

Suggestions

  • Just count the entries in the linked-list of clones and diplay in the job info box
  • Stop counting when more than 10 and say in the message "more than 10 times"
  • Optional: Flash popup when trying to clone a job that has already more than N (configurable in openQA config) clone origins

History

#1 Updated by mgrifalconi 4 months ago

+1
On daily aggregate runs it's something easy to see, but on incidents it's more tricky and would be helpful to see the data to better decide how to tackle the failure.

#2 Updated by okurz 4 months ago

  • Category set to Feature requests
  • Target version set to Ready

A valid and good idea

#3 Updated by okurz 4 months ago

I actually wanted to put that into future but misclicked :D but let's be nice and follow coolo's idea

#4 Updated by cdywan 4 months ago

  • Subject changed from Make the number of previous restarts easier available to Make the number of previous restarts of a job more discoverable size:M
  • Description updated (diff)
  • Status changed from New to Workable

#5 Updated by okurz 4 months ago

  • Parent task set to #105142

#6 Updated by mkittler 4 months ago

  • Status changed from Workable to In Progress
  • Assignee set to mkittler

#8 Updated by openqa_review 4 months ago

  • Due date set to 2022-02-04

Setting due date based on mean cycle time of SUSE QE Tools

#9 Updated by mkittler 4 months ago

  • Status changed from In Progress to Resolved

PR has been merged and deployed on OSD. It works, e.g. https://openqa.suse.de/tests/7991880.

#10 Updated by okurz 4 months ago

  • Due date deleted (2022-02-04)

Also available in: Atom PDF