autoscheduler should never schedule sessions at times in the past

Bug #779884 reported by Steve Langasek on 2011-05-09
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Summit
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. :)

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

Other bug subscribers