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

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

Jan Beulich writes ("Re: [Xen-devel] [xen-unstable test] 6532: regressions - 
trouble: broken/fail/pass"):
> > Tests which did not succeed and are blocking:
> >  test-amd64-amd64-pv           5 xen-boot                   fail REGR. vs. 
> > 6396
> 
> Seems like this is still failing at the same place in hpet.c, despite
> 23042:599ceb5b0a9b. Is the corresponding xen-syms available
> somewhere so I can sort out the condition to (hopefully) get a
> hint at what's still wrong?

In general you can find them by starting at this URL:

> > http://www.chiark.greenend.org.uk/~xensrcts/logs/6532/ 

You'll see a number of "build-" and "test-" columns.  Click on the
column heading for the failed test, in this case:

http://www.chiark.greenend.org.uk/~xensrcts/logs/6532/test-amd64-amd64-pv/info.html

and look for the table of "Test control variables".  There are entries
there for "xenbuildjob" (the hypervisor), "buildjob" (tools),
"kernbuildjob" (dom0 kernel).

Since you're asking for the Xen symbols file, you want the
"xenbuildjob" ie "build-amd64".  In fact, as it happens, all the tests
"test-amd64-*" use the same 64-bit hypervisor build from
"build-amd64".

So then you go back to the table and click on the "build-amd64" column
heading:

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

In the "Logfiles etc." click on "build/ (outputs from build)" and
download "xendist.tar.gz".  In the boot/ directory of that tarball are
the symbols.

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel