autoscheduler should never schedule sessions at times in the past

Bug #779884 reported by Steve Langasek
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Summit
Fix Released
Critical
Nigel Babu

Bug Description

Adding foundations-o-multiarch-next-steps to the uds-o sprint, the autoscheduler had scheduled it for me - at 10am on Monday, more than two hours in the past.

The autoscheduler should be fixed to know not to schedule sessions in the past. :)

Tags: linaro
Changed in summit:
importance: Undecided → Critical
Nigel Babu (nigelbabu)
Changed in summit:
assignee: nobody → Nigel Babu (nigelbabu)
Joey Stanford (joey)
tags: added: linaro
Nigel Babu (nigelbabu)
Changed in summit:
status: New → Fix Committed
Nigel Babu (nigelbabu)
Changed in summit:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.