Closed Bug 1063678 Opened 10 years ago Closed 9 years ago

Logviewer: Display step failures in the correct colour depending on the failure type

Categories

(Tree Management :: Treeherder, defect, P4)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: emorley, Assigned: camd, Mentored)

References

Details

(Whiteboard: [good first bug][lang=js])

User Story

Thank you for helping out with Treeherder!

You can find us on IRC at irc://irc.mozilla.org/treeherder

Here's some links to help get you started.

Project page:
https://wiki.mozilla.org/Auto-tools/Projects/Treeherder

Interacting with us, repo locations and links to set up a development version of the software:
https://wiki.mozilla.org/Auto-tools/Projects/Treeherder#Contributing
https://wiki.mozilla.org/Auto-tools/Projects/Treeherder#Source_and_Docs

A-Team general reference, coding style guides:
http://ateam-bootcamp.readthedocs.org
Bug 1043741 will mean that the logviewer has access to the result code for each step, however it currently only understands pass vs fail (passing steps are displayed green and failing orange). This bug is for mirroring the colours used in the main treeherder UI (eg retry == blue, usercancel == pink, ...). Since setting the colours involves a bit of messing about picking colours for border vs background and selected vs not, I've broken this out from bug 1043741, since it is less urgent.
Priority: P2 → P3
Component: Treeherder → Treeherder: Log Viewer
Priority: P3 → P4
This might be superseded by a larger logviewer redesign later on, but putting up as a good first bug for now.
Mentor: emorley
User Story: (updated)
Whiteboard: [good first bug]
Whiteboard: [good first bug] → [good first bug][lang=js]
User Story: (updated)
I believe this bug was addressed as a by product of bug 1057341 and PR https://github.com/mozilla/treeherder/pull/624 so marking fixed.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Assignee: nobody → cdawson
Component: Treeherder: Log Viewer → TreeHerder
You need to log in before you can comment on or make changes to this bug.