Wrong results in get_next_break with period >= 2 hours
Bug #215519 reported by
Sergey Lungu
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Workaholic |
New
|
Undecided
|
Unassigned | ||
Bug Description
When period >= 7200 get_next_break returns malformed time (eg 12:60). Patch, with less ridiculous way of doing the same thing, included.
Revision history for this message
| Sergey Lungu (lungu) wrote | #1 |
To post a comment you must log in.
