Race condition between Buildbucket and Scheduler |
||||
Issue descriptionThere appears to be a race condition between Buildbucket and Scheduler: when adding new Scheduler jobs, Scheduler might schedule Buildbucket builds before they are declared as backed by Swarming. This is because Buildbucket read config only after builds where created by Scheduler and as a consequence these are categorized as non-Swarming ones and they are stuck in the queue.
,
Jan 20 2017
,
Jan 20 2017
FTR, I'm not sure there's anything we can do. It's two independent systems reading configs at uncorrelated moments in time.
,
Oct 31 2017
What's the problem with first pushing configs to buildbucket, ensuring buildbucket processed them, and then adding configs for scheduler?
,
Oct 31 2017
It's just too tempting to commit two config files in a single commit, since they are in the same repo :)
,
Oct 31 2017
I see. Then, perhaps this should be renamed "Atomic config changes in luci-config", though I suspect it'll be wontfix for years anyways.
,
Oct 31 2017
changing something atomically in different apps is not easy indeed
,
Apr 30 2018
,
Apr 30 2018
eh, realistically, it is not going to happen |
||||
►
Sign in to add a comment |
||||
Comment 1 by benhenry@google.com
, Dec 1 2016