Re: [OSSTEST PATCH 05/28] sg-report-flight: Better searching for used revisions

[Ian Campbell <ian.campbell@citrix.com>]

On Tue, 2015-09-22 at 16:12 +0100, Ian Jackson wrote:
> The old algorithm used for determining which flight might be a
> suitable test of a particular revision was rather crude, in two ways:
> 
>  * It would look at _all_ jobs in a flight referred to from the flight
>    of interest, not just at the relevant jobs;
> 
>  * It would only look at the direct referents of the flight in
>    question.  So for example, if a flight of interest contained
>    test-amd64-i386-libvirt, it would find a referenced
>    build-i386-libvirt in another flight, but that build refers to
>    build-i386, and it would not look at that (unless it happened to be
>    in the same flight).
> 
> Fix this by redoing the revision archaeology, with some $why tracking
> to explain how we found a particular revision.
> 
> cs-bisection-step and sg-check-tested arguably ought to do do it this
> way too.  But I am leaving centralising this new logic, and using it
> in those other programs, for another day.
> 
> Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>

Acked-by: Ian Campbell <ian.campbell@citrix.com>