On Tue, 2015-05-05 at 18:47 +0100, Stefano Stabellini wrote:
I was suggesting ts-raisin-build could contain just 1. a call to raise
to list all the relevant trees 2. an iteration over the output,
copying information to/from runvars, 3. an exception table to allow
for situations like 'QEMU'
Stefano Stabellini writes (Re: [PATCH] OSSTEST: introduce a raisin build
test):
That's fine as there is no hidden git cloning with raisin. All the trees
are specified explicitly in the config file.
Is this a fundamental design principle ?
The rump kernel build system uses git submodules,
On Wed, 6 May 2015, Ian Jackson wrote:
Stefano Stabellini writes (Re: [PATCH] OSSTEST: introduce a raisin build
test):
That's fine as there is no hidden git cloning with raisin. All the trees
are specified explicitly in the config file.
Is this a fundamental design principle ?
The
On Wed, 6 May 2015, Ian Campbell wrote:
On Tue, 2015-05-05 at 18:47 +0100, Stefano Stabellini wrote:
I was suggesting ts-raisin-build could contain just 1. a call to raise
to list all the relevant trees 2. an iteration over the output,
copying information to/from runvars, 3. an exception
On 06/05/15 11:03, Stefano Stabellini wrote:
On Wed, 6 May 2015, Ian Jackson wrote:
Stefano Stabellini writes (Re: [PATCH] OSSTEST: introduce a raisin build
test):
That's fine as there is no hidden git cloning with raisin. All the trees
are specified explicitly in the config file.
Is this a
Ian Campbell writes (Re: [PATCH] OSSTEST: introduce a raisin build test):
On Fri, 2015-04-24 at 16:46 +0100, Stefano Stabellini wrote:
Signed-off-by: Stefano Stabellini stefano.stabell...@eu.citrix.com
This looks like a good start, a few comments below.
...
You should also call
On Tue, 5 May 2015, Ian Campbell wrote:
On Fri, 2015-04-24 at 16:46 +0100, Stefano Stabellini wrote:
Signed-off-by: Stefano Stabellini stefano.stabell...@eu.citrix.com
This looks like a good start, a few comments below.
diff --git a/ap-common b/ap-common
index 64749e3..985eeec 100644
Stefano Stabellini writes (Re: [PATCH] OSSTEST: introduce a raisin build
test):
I agree that revisions should be passed to ts-raisin-build by osstest,
as Ian suggested. AFAICT that should be enough to meet all your
criteria.
You also need to call store_revision for all the trees involved, as
On Tue, 5 May 2015, Ian Jackson wrote:
Ian Campbell writes (Re: [PATCH] OSSTEST: introduce a raisin build test):
On Fri, 2015-04-24 at 16:46 +0100, Stefano Stabellini wrote:
Signed-off-by: Stefano Stabellini stefano.stabell...@eu.citrix.com
This looks like a good start, a few comments
On Fri, 2015-04-24 at 16:46 +0100, Stefano Stabellini wrote:
Signed-off-by: Stefano Stabellini stefano.stabell...@eu.citrix.com
This looks like a good start, a few comments below.
diff --git a/ap-common b/ap-common
index 64749e3..985eeec 100644
--- a/ap-common
+++ b/ap-common
@@ -47,13
On Tue, 5 May 2015, Ian Jackson wrote:
Stefano Stabellini writes (Re: [PATCH] OSSTEST: introduce a raisin build
test):
I agree that revisions should be passed to ts-raisin-build by osstest,
as Ian suggested. AFAICT that should be enough to meet all your
criteria.
You also need to call
Signed-off-by: Stefano Stabellini stefano.stabell...@eu.citrix.com
---
ap-common |5 +++
mfi-common | 19 ++
sg-run-job |5 +++
ts-raisin-build | 104 +++
4 files changed, 133 insertions(+)
create mode 100755
12 matches
Mail list logo
