On Wed, 2015-09-16 at 14:35 +0100, Ian Jackson wrote: > Previously the flight to delete was simply the one with the lowest > flight number. Now we sort flights not by their own flight number, > but by the highest flight number of any referencing flight. > > This means that flights whose builds are being reused are kept as long > as the reusing flights. > > This almost-entirely fixes a largely-theoretical race in the way > cs-bisection-step works (where the flight's logs and build outputs > might be deleted between the setup and execution of the referring > flight). > > A smaller race still exists because the stash check in > cs-bisection-step occurs before the being-created flight is visible to > other db clients. We will have to fix this by taking the flights > lock. > > Signed-off-by: Ian Jackson <ian.jack...@eu.citrix.com>
Acked-by: Ian Campbell <ian.campb...@citrix.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
