Project

General

Profile

Actions
Copy link

action #107878

closed

number of failed job provides wrong value on the build's status bar

Added by ybonatakis about 2 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Low
Assignee:
mkittler
Category:
Regressions/Crashes
Target version:
Ready
Start date:
2022-03-04
Due date:
2022-03-18
% Done:

0%

Estimated time:

Description

https://openqa.suse.de/group_overview/130 display 2 failed jobs for build101.1.

if you press on the failed area of the bar, the Test result overview shows only one failed job. Cleaning all the filters i see that the only other job which was not successful is one failed as timeout_exceeded.

So either the failed area should enabled the Timeout exceeded(or any other flag) or it bar should point out only the actual failed jobs.

Actions
Copy link
 #1

Updated by mkittler about 2 years ago

  • Assignee set to mkittler
Actions
Copy link
 #2

Updated by mkittler about 2 years ago

  • Status changed from New to In Progress
Actions
Copy link
 #3

Updated by mkittler about 2 years ago

  • Status changed from In Progress to Feedback

The PR has already been merged. Let me know if this is what you had in mind with "the failed area should enabled the Timeout exceeded".

Actions
Copy link
 #4

Updated by okurz about 2 years ago

  • Due date set to 2022-03-18
  • Priority changed from Normal to Low
  • Target version set to Ready
Actions
Copy link
 #5

Updated by mkittler about 2 years ago

  • Status changed from Feedback to Resolved

It should be ok. You can still set the ticket back to feedback if I misunderstood you.

Actions
Copy link

Also available in: Atom PDF