From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH OSSTEST] make-flight: Support specifying a mini-os tree+revision
Date: Fri, 15 Jan 2016 16:28:52 +0000 [thread overview]
Message-ID: <1452875332.6020.71.camel@citrix.com> (raw)
In-Reply-To: <1450258366.16856.214.camel@citrix.com>
On Wed, 2015-12-16 at 09:32 +0000, Ian Campbell wrote:
> On Fri, 2015-12-11 at 15:16 +0000, Ian Jackson wrote:
> > Ian Campbell writes ("[PATCH OSSTEST] make-flight: Support specifying a
> > mini-os tree+revision"):
> > > This is useful for standalone or adhoc use as well as (presumably)
> > > bisection.
> > >
> > > There is no ap-* or cr-daily-* integration here because I didn't need
> > > it (i.e. I'm not intending to create a new mini-os branch here).
> >
> > Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
>
> This patch fails when building 4.5 and earlier because
Any thoughts on what to do here? i.e. the plan in the second half of the
final paragraph.
> extras/mini-os
> exists but is part of xen.git not a separate repo, so dir_identify_vcs
> goes:
>
> 2015-12-15 17:21:50 Z executing ssh ... osstest@10.80.229.171
> cd /home/osstest/build.38523.build-amd64/xen/tools/firmware/ovmf-dir &&
> git rev-parse HEAD^0
> 2015-12-15 17:21:50 Z runvar store: built_vcs_ovmf=git
> 2015-12-15 17:21:50 Z runvar store:
> built_revision_ovmf=cb9a7ebabcd6b8a49dc0854b2f9592d732b5afbd
> 2015-12-15 17:21:50 Z executing ssh ... osstest@10.80.229.171
> set -e
> if ! test -e /home/osstest/build.38523.build-
> amd64/xen/extras/mini-os; then echo none; exit 0; fi
> cd /home/osstest/build.38523.build-amd64/xen/extras/mini-os
> (test -e .git && echo git) ||
> (test -d .hg && echo hg) ||
> (echo >&2 'unable to determine vcs'; fail)
>
> unable to determine vcs
> bash: line 5: fail: command not found
>
> I'm not sure if this is a bug (i.e. it was intended to be "echo fail") or
> if it is deliberately using a non-existent command (which seems risky to
> me).
>
> All the other store_revisions refer to the symlink rather than the -remote
> which is the actual clone (when one is made), so I don't think
> s#extras/mini-os#extras/mini-os-remote# is the answer. Perhaps "fail"
> should become "echo fail" and store_revision should treat that like it does
> fail (which is to accept it if $optional).
>
> Ian.
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-01-15 16:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 13:56 [PATCH OSSTEST] make-flight: Support specifying a mini-os tree+revision Ian Campbell
2015-12-11 15:16 ` Ian Jackson
2015-12-16 9:32 ` Ian Campbell
2016-01-15 16:28 ` Ian Campbell [this message]
2016-01-15 17:07 ` Ian Jackson
2016-01-15 17:40 ` 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=1452875332.6020.71.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
/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.