Project

Profile

Help

Task #2752

closed

As a user, I can identify for which node unittests failed without checking every log

Added by ttereshc about 5 years ago. Updated about 3 years ago.

Status:
CLOSED - COMPLETE
Priority:
Normal
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
Target Release - Packaging:
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Sprint 20
Quarter:

Description

If unittests fail for F25 only and pass for the rest of nodes, one has to go through every log here [0] and find out if it is the failed one or not.

It would be nice to have one more column on this page [0] which will say something like passed/failed or green/red (to mimic jenkins).

[0] https://pulpadmin.fedorapeople.org/jenkins/jobs/unittest-pulp-pr/builds/650/

Actions #1

Updated by ttereshc about 5 years ago

  • Subject changed from As a user, I can identiy for which node unittests failed without checking every log to As a user, I can identify for which node unittests failed without checking every log
Actions #2

Updated by mhrivnak almost 5 years ago

  • Sprint/Milestone set to 39

Added by dkliban@redhat.com almost 5 years ago

Revision 131156fa

Problem: unit test results don't highlight failure

Solution: append FAILED to the build log file name when failure is detected.

closes #2752

Actions #3

Updated by dkliban@redhat.com almost 5 years ago

  • Status changed from NEW to MODIFIED
  • % Done changed from 0 to 100
Actions #4

Updated by dkliban@redhat.com almost 5 years ago

  • Tracker changed from Story to Task
  • Status changed from MODIFIED to CLOSED - COMPLETE
  • Assignee set to dkliban@redhat.com
Actions #5

Updated by bmbouter about 4 years ago

  • Sprint set to Sprint 20
Actions #6

Updated by bmbouter about 4 years ago

  • Sprint/Milestone deleted (39)
Actions #7

Updated by bmbouter about 3 years ago

  • Tags Pulp 2 added

Also available in: Atom PDF