Closed
Bug 990828
Opened 11 years ago
Closed 11 years ago
Display Most recent 10 slaveapi calls, not oldest 10
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Callek, Assigned: Callek)
Details
Attachments
(1 file)
1.84 KB,
patch
|
jhopkins
:
review+
|
Details | Diff | Splinter Review |
So in slave health we do properly sort the results, and properly list them so newest result is at top, however we stop populating after 10 entries, which means we also stop entering the most-recent ones, if there are more than 10 entries to look at.
This patch also makes sure the requested entry gets sorted in the spot where it was requested, with text for "In Progress" (no code to update the table when its done though)
Note that until Bug 990814 is checked in and deployed the request_time won't be real useful for this sorting.
Attachment #8400319 -
Flags: review?(jhopkins)
Comment 1•11 years ago
|
||
Comment on attachment 8400319 [details] [diff] [review]
[slave_health] v1
Looks good to me. Just one nit:
+ if (sorted_reboots[i].start_timestamp != 0) {
Remove "!= 0" to match byStartTimestamp comparison higher up.
Attachment #8400319 -
Flags: review?(jhopkins) → review+
Assignee | ||
Comment 2•11 years ago
|
||
landed, should deploy automatically.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•8 years ago
|
Component: Tools → General
You need to log in
before you can comment on or make changes to this bug.
Description
•