#246: Add temporary hack for test re-scheduling --------------------+------------------------------------------------------- Reporter: kparal | Owner: Type: task | Status: new Priority: major | Milestone: 0.4.4 Component: core | Resolution: Keywords: | --------------------+------------------------------------------------------- Comment (by jlaska):
Replying to [ticket:246 kparal]:
- get a list of use cases for which we need to reschedule upgradepath
or depcheck
Good point. I think this would be helpful regardless to get a sense for how frequent the issue is.
- inquire whether Bodhi changes timestamp (or whatever) of the updates
in those cases (i.e. we would detect it and run tests again properly even with our current watcher implementation)
- in the remaining cases decide what to do with it. For example we can
make temporary upgradepath behave the same way as depcheck does, i.e. test all builds in -updates-pending for every update of that tag. Because we will have Bodhi comment duplication prevention, it could work quite fine.
That depcheck approach maybe our best method yet.