From: Ian Campbell <ian.campbell@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
xen-devel@lists.xen.org
Cc: wei.liu2@citrix.com, ian.jackson@eu.citrix.com
Subject: Re: [PATCH v8 1/2] OSSTEST: introduce a raisin build test
Date: Tue, 4 Aug 2015 12:04:31 +0100 [thread overview]
Message-ID: <1438686271.31129.96.camel@citrix.com> (raw)
In-Reply-To: <1437670366-29034-1-git-send-email-stefano.stabellini@eu.citrix.com>
On Thu, 2015-07-23 at 17:52 +0100, Stefano Stabellini wrote:
> +sub build () {
> + target_cmd_build($ho, 9000, $builddir, <<END);
> + cd $raisindir
> + ./raise -n build
> +END
> +#/;
Running this is pretty quiet it seems, which is normally good but I think
for automated test we likely want to crank up the verbosity somewhat. Is
that possible?
Or else if this is being captured into some logfile somewhere we should
capture that.
It also said:
[raisin] Missing packages: pciutils-dev
which I guess is something which needs to be added to ts-xen-build-prep?
It hasn't actually failed though, is that normal?
It also said
[raisin] Raisin requires sudo to install build dependencies for you.
[raisin] You can only build without it.
but I think that is desirable/expected. Not installing sudo on osstest
build hosts (as we do) seems like a good safety catch to maintain to me.
Ian.
next prev parent reply other threads:[~2015-08-04 11:04 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 16:51 [PATCH v8 0/2] OSSTEST: introduce a raisin build test Stefano Stabellini
2015-07-23 16:52 ` [PATCH v8 1/2] " Stefano Stabellini
2015-07-31 15:53 ` Ian Jackson
2015-07-31 15:54 ` Ian Jackson
2015-07-31 16:01 ` Ian Jackson
2015-08-03 16:59 ` Stefano Stabellini
2015-08-04 10:55 ` Ian Campbell
2015-08-04 13:02 ` [PATCH 1/2] ts-raisin-build: consolidate open coded iterations over enabled components Ian Campbell
2015-08-05 7:50 ` Ian Campbell
2015-08-04 13:02 ` [PATCH 2/2] ts-raisin-build: Use git_massage_url Ian Campbell
2015-08-04 8:35 ` [PATCH v8 1/2] OSSTEST: introduce a raisin build test Ian Campbell
2015-08-04 8:39 ` Ian Campbell
2015-08-04 9:37 ` Ian Campbell
2015-08-04 13:26 ` Stefano Stabellini
2015-08-04 11:04 ` Ian Campbell [this message]
2015-08-04 11:18 ` Stefano Stabellini
2015-08-04 11:37 ` Ian Campbell
2015-08-04 13:18 ` Stefano Stabellini
2015-08-04 13:41 ` Ian Campbell
2015-08-04 13:47 ` Stefano Stabellini
2015-08-04 14:01 ` Ian Campbell
2015-08-04 13:47 ` Roger Pau Monné
2015-08-04 13:51 ` Ian Campbell
2015-07-23 16:52 ` [PATCH v8 2/2] OSSTest: push successful raisin builds Stefano Stabellini
2015-07-31 16:03 ` Ian Jackson
2015-08-03 17:09 ` Stefano Stabellini
2015-08-04 8:23 ` Ian Campbell
2015-08-04 10:50 ` Ian Campbell
2015-08-04 12:56 ` Ian Campbell
2015-08-04 13:11 ` 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=1438686271.31129.96.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@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.