Re: [Xen-devel] [xen-unstable test] 17327: trouble: broken/fail/pass

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

Jan Beulich writes ("Re: [Xen-devel] [xen-unstable test] 17327: trouble: 
broken/fail/pass"):
> >>> On 19.03.13 at 03:36, xen.org <ian.jackson@xxxxxxxxxxxxx> wrote:
> > flight 17327 xen-unstable real [real]
> > http://www.chiark.greenend.org.uk/~xensrcts/logs/17327/ 
...
> I don't see how I could prove that. Is there any other way to
> associate the log of a particular run with the top level commit of
> the originating source tree?

If you look at one of the build-* columns (click on the column
heading) you see a table of "Test control variables".  Here, for
example:

http://www.chiark.greenend.org.uk/~xensrcts/logs/17327/build-amd64/info.html

There you can see the revisions of the various trees used.  It also
does a check afterwards (using "git-rev-parse HEAD", for example) and
records the result as built_revision_...

So did indeed use xen.git 2d8a2823f3d6d2e5fba832e0afe1fab8fbcb3694.

(Bisection jobs may reuse other builds so you may need to check the
test column variables for the "xenbuildjob" etc. variables.)

Ian.

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