Closed Bug 757879 Opened 12 years ago Closed 12 years ago

Consider removing the concept of latest job of each type

Categories

(Tree Management Graveyard :: TBPL, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: emorley, Assigned: emorley)

References

Details

Attachments

(1 file)

Following on from bug 656732 comment 10.

Bug 656732 is removing the failing job squares from the top right TBPL status panel. This just leaves the tab title and the "N Jobs is/are failing" string that use the concept of the latest job for each type of run. 

If we decided that having the tab title/other string display the total unstarred jobs, and not just of each type, then we could do a fair amount more cleanup.
Sorry, the last sentence should read:

If we decided that having the tab title/other string display the total unstarred jobs, and not just of each type, was acceptable (or even preferable, given it shows how much work the tree needs in terms of starring), then we could do a fair amount more cleanup.
Summary: Remove concept of latest job of each type → Consider removing the concept of latest job of each type
Attached patch Patch v1Splinter Review
Patch for if we go ahead with this. Think I've got everything that can be cleaned out.
Assignee: nobody → bmo
Status: NEW → ASSIGNED
Attachment #627249 - Flags: review?(arpad.borsos)
Comment on attachment 627249 [details] [diff] [review]
Patch v1

Review of attachment 627249 [details] [diff] [review]:
-----------------------------------------------------------------

Awesome!
I need to take a deeper look at this myself, maybe i find something as well.
Haven`t been around that code for a while.

::: js/UserInterface.js
@@ +786,5 @@
>        }
>      }
>  
>      $('#status').get(0).innerHTML = (function calcHTML() {
> +      return '<strong>' + failing.length + '</strong> Unstarred';

This should be `unstarred`. You can probably add both failing and unstarred in there.
Attachment #627249 - Flags: review?(arpad.borsos) → review+
Failing might be interesting if someone wants to write a "display failing when we're displaying a single push" patch, but in general, let's not. I haven't refreshed since I woke up, so my mozilla-inbound tab is displaying 20 or 30 pushes, and I don't have any need whatsoever to be told that that's "120 failing" or "180 failing" or whatever it is.
(In reply to Arpad Borsos (Swatinem) from comment #3)
> This should be `unstarred`.

I capitalised it to match "N Jobs...". I don't really mind either way though...
Ah! You meant use the variable unstarred instead of failing.length, rather than talking about the capitalisation of the string 'unstarred', sorry that makes more sense. (Just realised what you meant after testing locally and spotting that the tab title wasn't matching the number shown in-page).

Landed with that change:
http://hg.mozilla.org/users/mstange_themasta.com/tinderboxpushlog/rev/b5e2ef235e55
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Yep that is what i meant. Thanks!
Depends on: 760321
Product: Webtools → Tree Management
Product: Tree Management → Tree Management Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: