[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [xen-4.6-testing test] 64270: regressions - FAIL
On Mon, 2015-11-16 at 04:56 -0700, Jan Beulich wrote: > > > > On 15.11.15 at 10:26, <osstest-admin@xxxxxxxxxxxxxx> wrote: > > flight 64270 xen-4.6-testing real [real] > > http://logs.test-lab.xenproject.org/osstest/logs/64270/ > > > > Regressions :-( > > > > Tests which did not succeed and are blocking, > > including tests which could not be run: > > Âbuild-amd64-prevÂÂÂÂÂÂÂÂÂÂÂÂÂÂ5 xen-buildÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂfail REGR. > > vs. 63449 > > Âbuild-i386-prevÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ5 xen-buildÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂfail REGR. > > vs. 63449 > > if test -d http://xenbits.xen.org/git-http/qemu-upstream-4.5-testing.git > ; then \ > mkdir -p qemu-xen-dir; \ > else \ > export GIT=git; \ > /home/osstest/build.64270.build-amd64- > prev/xen/tools/../scripts/git-checkout.sh http://xenbits.xen.org/git-http > /qemu-upstream-4.5-testing.git qemu-xen-4.5.2 qemu-xen-dir ; \ > fi > Cloning into 'qemu-xen-dir-remote.tmp'... > fatal: git checkout: updating paths is incompatible with switching > branches. > Did you intend to checkout 'qemu-xen-4.5.2' which can not be resolved as > commit? > make[2]: *** [qemu-xen-dir-find] Error 128 > > I have to admit that I have no idea what's going on here (and why > we see this only on 4.6). At a guess, since we switched to a single qemu tree per version the tags have not been pushed to the old trees (osstest looks to only update the branches). That doesn't explain why the real 4.5 flights aren't seeing this though (this job is building the N-1 version for migration upgrade testing). I think if the 4.6 release cycle is at a suitable point we should backport the Cofnig.mk change to switch to the combined trees. If that would be inappropriate right now then pushing the tags by hand to the old tree would be ok. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |