Closed Bug 797811 Opened 8 years ago Closed 5 years ago

Make OrangeFactor show results from the current day too

Categories

(Tree Management :: OrangeFactor, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: emorley, Assigned: emorley)

References

Details

(Keywords: sheriffing-P1)

Attachments

(2 files)

It would be useful for sheriffs to be able to see OrangeFactor results as they came in/were processed, rather than only displaying everything up to the end of the previous day.
Blocks: 807273
No longer blocks: 807273
Blocks: 817268
Assignee: nobody → edmorley.bz
Status: NEW → ASSIGNED
Keywords: sheriffing-P1
Whiteboard: [sheriff-want]
Not actively working on this right now, may come back to later, but for now sticking back in the pool.
Assignee: emorley → nobody
Status: ASSIGNED → NEW
Product: Testing → Tree Management
If we turn bug comments off, this is more important, since otherwise we have no other way to see recent occurrences of a bug.
Assignee: nobody → emorley
Blocks: 1179310
Status: NEW → ASSIGNED
Note to self:

Pushlog is effectively exclusive on the end date, since:
startdate=2015-07-05&enddate=2015-07-06

Results in:
"Changes pushed after 2015-07-05 00:00:00, before 2015-07-06 00:00:00"
(See http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?startdate=2015-07-05&enddate=2015-07-06)

Alternatively we could just use the time too, eg:
http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?startdate=2015-07-05&enddate=2015-07-06%2019:28:19
Attachment #8630229 - Flags: review?(jgriffin)
Attachment #8630229 - Flags: review?(jgriffin) → review+
Attachment #8630229 - Flags: checkin+
Attachment #8630399 - Flags: review?(jgriffin) → review+
Comment on attachment 8630399 [details] [diff] [review]
The date picker should allow startday & endday to be the same date

https://hg.mozilla.org/automation/orangefactor/rev/aaa599c22a0a
Attachment #8630399 - Flags: checkin+
Deployed.
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.