As @dtzWill discovered, with the concurrent hydra-evaluator, there can be multiple active transactions adding builds to the database. As a result, builds can become visible in a non-monotonically increasing order, breaking the queue monitor's assumption that build IDs only go up. The fix is to have hydra-eval-jobset provide the lowest build ID it just added in the builds_added notification, and have the queue monitor check from there. Fixes #496.
3 lines
71 B
SQL
3 lines
71 B
SQL
drop trigger BuildsAdded on Builds;
|
|
drop function notifyBuildsAdded();
|