Re: [Xen-devel] [OSSTEST PATCH 6/6] sg-run-job: Do blocked check globally, in run-job

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

Ian Campbell writes ("Re: [OSSTEST PATCH 6/6] sg-run-job: Do blocked check 
globally, in run-job"):
> On Wed, 2014-05-21 at 12:42 +0100, Ian Jackson wrote:
> > Only run-job can fully abandon the whole job.  With the previous
> > arrangements (in bc63a901), a blocked build job would go on to try to
> > run ts-logs-capture and become broken (rather than blocked).
> > 
> > The downside of this is that it is not possible in the future to
> > introduce a kind of job which can selectively carry on if some of its
> > dependencies fail.  This notion is IMO an acceptable casualty.
> 
> Just to be clear: This doesn't exclude the existing behaviour of
> ts-migrate-support-check, does it? (I think not because you talk about
> jobs and this is a step)

Indeed, that remains unaffected.  We're talking here only about
inter-job dependencies which show up in "*buildjob" runvars.

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel