#420: Some builds are tested many times over --------------------+------------------------- Reporter: kparal | Owner: jskladan Type: defect | Status: reopened Priority: major | Milestone: Hot issues Component: tests | Resolution: Keywords: | Blocked By: Blocking: | --------------------+-------------------------
Comment (by jskladan):
OK, I've identified the issue - the problem is, that when we check update- candidates builds, there might be some "yet untagged" in Koji. And since koji/bodhi watcher needs to output the kojitag as one of the parameters, we are storing these 'untagged' builds for next runs. This is not really a problem but:
1) to make sure we don't query/test too much builds, we store the last "completion_ts" of all the builds to be tested
2) in next run, we take the stored completion_ts, and ask koji for all builds completed since.
3) in case, when no new builds are returned by koji AND there were some stored 'untagged builds', the last 'completion_ts' is taken from the 'untagged builds' set, therefore setting the last "completion_ts" into past.
Solution should be quite simple, I'm working on it already.