> Subject: Re: FW: [Xen-devel] test structure missing files
> From: Ian.Campbell@xxxxxxxxxx
> To: johneed@xxxxxxxxxxx
> CC: xen-devel@xxxxxxxxxxxxxxxxxxx
> Date: Wed, 26 Oct 2011 07:25:49 +0100
>
> In general the interesting stuff will likely be in the few lines before
> the actual error, in particular the gcc invocation and sometimes the
> make output about which directory it is building in etc. Please be wary
> of trimming too much when posting error messages.
>
roger that
> I just managed to reproduce the error though, it was non-obvious because
> I had to run "make clean" in the tools tree first. I think you need to
> have built the tools tree before running the test target, at least this
> seems logical and works for me.
>
roger that. Now you mention it, indeed. I was attempting to cut it down to bare minimum
in response to your mentioning things such as patches and commands which might have an impact.
Took it too far. Now for a more sensible approach..
> I suppose we should find a way to show this in the top-level Makefile
> dependencies. Perhaps this is sufficient:
>
> diff -r e6af32ecb448 Makefile
> --- a/Makefile Tue Oct 18 14:15:09 2011 +0100
> +++ b/Makefile Wed Oct 26 07:23:05 2011 +0100
> @@ -31,7 +31,7 @@ endif
> # course, many tests require a machine running Xen itself, and these are
> # handled elsewhere.
> .PHONY: test
> -test:
> +test: tools
> $(MAKE) -C tools/python test
>
> # build and install everything into local dist directory
>
> I get failures now because I didn't build/test on a Xen host. That might
> be a show stopper for an ebuild as well?
>
> Ian.
>
After kicking my system into a better shape by way of the curl library and rebuilding xen-tools with the
gentoo api use flag, I have some sanity now produced from running the make test. Importantly any
trace of those initial errors now don't appear. This means the test suite is now usable and
incorporatable into an ebuild. Seems the running of the test suite will be conditional on selection
of some gentoo use flags. Still get errors.
Ran 9 tests in 0.080s
FAILED (failures=1, errors=5)
ImportError: cannot import name XendConfig
ValueError: Cannot find kernel "/mykernel"
ValueError: Cannot find kernel "/boot/vmlinuz-xenU-smp"
AssertionError: videoram not in b
which makes 4, each of these repeated a couple of times. Some gentoo python devs ought be able to
troubleshoot these. If you would like the test build log, just say so. From here it's purely python.
At a glance I suspect the tests that trigger "/mykernel" && "/boot/vmlinuz-xenU-smp" could be
commented out or deleted IF they stem from requiring the source to build kernels, which
does not occur in a xen-tools package. gentoo makes xen for the hypervisor, xen-tools and of recent
xen-pvgrub which is an invocation of make install-stubdom. I shall call upon more python fluent
gentoo devs to determine such states.
In the unlikely case that the gentoo devs can't sort these python misfires I shall need return and
prompt for further support.
Thanks
Ian Delaney, gentoo xen
Home