Re: [Xen-devel] [xen-4.2-testing test] 16690: regressions - FAIL

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 26.02.13 at 12:11, xen.org <ian.jackson@xxxxxxxxxxxxx> wrote:
> flight 16690 xen-4.2-testing real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/16690/ 
> 
> Regressions :-(
> 
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>  build-amd64-oldkern           4 xen-build                 fail REGR. vs. 
> 16228
>  build-i386-oldkern            4 xen-build                 fail REGR. vs. 
> 16228

The kernel build didn't even start when these failed, yet the
real reason for the failure also isn't clear to me. Trying to glue
together the matching pieces, I think is goes like this:

make[2]: Entering directory 
`/home/osstest/build.16690.build-i386-oldkern/xen-unstable'
set -e ; \
        if [ ! -e linux-2.6.18-xen.hg/.hg ] ; then \
            __repo=http://xenbits.xen.org/linux-2.6.18-xen.hg ; \
            if [ -d ${__repo} ] ; then \
                echo "Linking ${__repo} to linux-2.6.18-xen.hg." ; \
                ln -s ${__repo} linux-2.6.18-xen.hg ; \
            else \
                echo "Cloning ${__repo} to linux-2.6.18-xen.hg." ; \
                hg clone ${__repo#file://} linux-2.6.18-xen.hg ; \
            fi ; \
        else \
            __parent=$(hg -R linux-2.6.18-xen.hg path default) ; \
            echo "Pulling changes from ${__parent} into linux-2.6.18-xen.hg." ; 
\
            hg -R linux-2.6.18-xen.hg pull ${__parent} ; \
        fi
Cloning http://xenbits.xen.org/linux-2.6.18-xen.hg to linux-2.6.18-xen.hg.
...
requesting all changes
adding changesets
adding manifests
adding file changes
transaction abort!
rollback completed
abort: Connection reset by peer
make[2]: Leaving directory 
`/home/osstest/build.16690.build-i386-oldkern/xen-unstable'
make[2]: *** [linux-2.6.18-xen.hg/.valid-src] Error 255
make[1]: *** [linux-2.6-xen-install] Error 2
make: *** [install-kernels] Error 1
make[1]: Leaving directory 
`/home/osstest/build.16690.build-i386-oldkern/xen-unstable'

The odd thing being that neither 4.1 nor master had similar
problems in their tests. Do we simply need to wait for another
run?

Jan


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