cannot ignore historical times when scheduling tests
Bug #1436547 reported by
Leah Klearman
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Testrepository |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
When historical times are known-bad, the next test run may be very poorly scehduled. This is in part because its an offline scheduler, and in part because if e.g. some normally fast tests went very slow, you get substantial skew.
Leah suggests - set TESTR_SCHED_
| Changed in testrepository: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
| summary: |
- make it possible to ignore times.dbm + cannot ignore historical times when scheduling tests |
| description: | updated |
To post a comment you must log in.
