From: Ian Campbell <ian.campbell@citrix.com>
To: "xen.org" <Ian.Jackson@eu.citrix.com>, Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [xen-4.3-testing test] 36526: regressions - FAIL
Date: Fri, 20 Mar 2015 09:36:20 +0000 [thread overview]
Message-ID: <1426844180.21742.98.camel@citrix.com> (raw)
In-Reply-To: <osstest-36526-mainreport@xen.org>
On Thu, 2015-03-19 at 23:31 +0000, xen.org wrote:
> flight 36526 xen-4.3-testing real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/36526/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> build-i386 5 xen-build fail REGR. vs. 36483
> build-amd64 5 xen-build fail REGR. vs. 36483
http://www.chiark.greenend.org.uk/~xensrcts/logs/36526/build-amd64/5.ts-xen-build.log:
fatal: git checkout: updating paths is incompatible with switching branches.
Did you intend to checkout 'xen-4.3.4' which can not be resolved as commit?
make[1]: *** [qemu-xen-traditional-dir-find] Error 128
It seems I failed to run git update-server-info when pushing the
qemu-xen tags here and to 4.4-testing yesterday (despite the
release-checklist clearly telling me to do so).
xen@xenbits$ for i in qemu-xen-4.3-testing.git/ qemu-xen-4.4-testing.git/ ; do
> (cd $i && git update-server-info)
> (cd staging/$i && git update-server-info)
> done
The next 4.3-testing flight 36551 has also hit this issue, but was
waiting to test ARM, so I have killed it so a new one will get kicked
off with this fix in place.
The ongoing 4.4-testing flight seems to have used git:// URLs and so is
unaffected.
Ian.
prev parent reply other threads:[~2015-03-20 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 23:31 [xen-4.3-testing test] 36526: regressions - FAIL xen.org
2015-03-20 9:36 ` Ian Campbell [this message]
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=1426844180.21742.98.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.