From: Ian Campbell <ian.campbell@citrix.com>
To: osstest service owner <osstest-admin@xenproject.org>,
xen-devel@lists.xensource.com, stefano.stabellini@eu.citrix.com
Subject: Re: [xen-4.3-testing test] 62392: tolerable FAIL - PUSHED
Date: Thu, 8 Oct 2015 09:51:56 +0100 [thread overview]
Message-ID: <1444294316.1410.102.camel@citrix.com> (raw)
In-Reply-To: <osstest-62392-mainreport@xen.org>
On Mon, 2015-09-28 at 04:48 +0000, osstest service owner wrote:
> Tests which did not succeed, but are not blocking:
>
[...]
> build-amd64-prev 5 xen-build fail never pass
> build-i386-prev 5 xen-build fail never pass
TL;DR: Missing git-http symlink on xenbits for qemu-upstream-4.2
-testing.git, now fixed.
http://logs.test-lab.xenproject.org/osstest/logs/62392/build-amd64-prev/5.ts-xen-build.log
Contains:
fatal: http://xenbits.xen.org/git-http/qemu-upstream-4.2-testing.git/info/refs not found: did you run git update-server-info on the server?
(as does the build-i386-prev one).
Interestingly from my workstation I get:
$ git clone http://xenbits.xen.org/git-http/qemu-upstream-4.2-testing.git
Cloning into 'qemu-upstream-4.2-testing'...
fatal: repository 'http://xenbits.xen.org/git-http/qemu-upstream-4.2-testing.git/' not found
Whereas from the colo I get:
$ git clone http://xenbits.xen.org/git-http/qemu-upstream-4.2-testing.git
Cloning into 'qemu-upstream-4.2-testing'...
fatal: http://xenbits.xen.org/git-http/qemu-upstream-4.2-testing.git/info/refs not found: did you run git update-server-info on the server?
This doesn't affect the build-{amd64,i386} jobs because they get the git
variant via a runvar, whereas the -prev jobs accept the default from
Config.mk, and we set GIT_HTTP=y in ts-xen-build (which is another question
I suppose!).
I ran update-server-info command in the repo on xenbits, but it didn't
help. Then I noticed the symlink was missing from /var/xenbits-www/html/git
-http. The manual clones are now working.
I'm considering manually forcing a rerun of xen-4.3-testing even though no
changes are pending because I think it would be nice to have an unbroken
chain of passes for test-amd64-{amd64,i386}-migrupgrade step by step all
the way from 4.1 to 4.6... Other than this there is a separate issue with
the build-*-prev in xen-4.4-testing which I'll fix too.
Ian.
next prev parent reply other threads:[~2015-10-08 8:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-28 4:48 [xen-4.3-testing test] 62392: tolerable FAIL - PUSHED osstest service owner
2015-10-08 8:51 ` Ian Campbell [this message]
2015-10-09 7:57 ` Ian Campbell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1444294316.1410.102.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=osstest-admin@xenproject.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).