From: David Vrabel <david.vrabel@citrix.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: xen-devel@lists.xenproject.org, Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [OSSTEST PATCH 0/3] test linux-next
Date: Mon, 14 Apr 2014 12:14:34 +0100 [thread overview]
Message-ID: <534BC31A.4010704@citrix.com> (raw)
In-Reply-To: <1397471610-25399-1-git-send-email-ian.jackson@eu.citrix.com>
On 14/04/14 11:33, Ian Jackson wrote:
> We need a different approach to selecting a baseline for testing
> linux-next. I have tested this series and it appeared to work - the
> results can be found in this email on xen-devel:
>
> Subject: [linux-next test] 25862: tolerable FAIL
> Date: Sat, 12 Apr 2014 00:28:06 +0100
>
> (The test results were a complete disaster because the linux tip on
> which this linux-next was based cannot boot under Xen. See flight
> 25840. I.e. the failures are a bug in Linux, not in the tester.)
>
> 1/3 sg-check-tested: add "use strict"
> 2/3 sg-check-tested: support --git-ancestor-of
> 3/3 cr-*, ap-*: Facilities for testing linux-next
The first run of this was a disaster. Unless someone can allocate time
(not me, I have no spare time) to triage/improve this run I don't think
this is going to be useful for regression testing.
David
next prev parent reply other threads:[~2014-04-14 11:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 10:33 [OSSTEST PATCH 0/3] test linux-next Ian Jackson
2014-04-14 10:33 ` [OSSTEST PATCH 1/3] sg-check-tested: add "use strict" Ian Jackson
2014-04-14 10:33 ` [OSSTEST PATCH 2/3] sg-check-tested: support --git-ancestor-of Ian Jackson
2014-04-14 10:33 ` [OSSTEST PATCH 3/3] cr-*, ap-*: Facilities for testing linux-next Ian Jackson
2014-04-14 10:37 ` Ian Campbell
2014-04-14 11:04 ` Ian Jackson
2014-04-14 11:07 ` Ian Campbell
2014-04-14 14:38 ` Ian Jackson
2014-04-14 11:14 ` David Vrabel [this message]
2014-04-14 14:39 ` [OSSTEST PATCH 0/3] test linux-next Ian Jackson
2014-04-25 9:22 ` Ian Campbell
2014-04-30 14:55 ` Ian Jackson
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=534BC31A.4010704@citrix.com \
--to=david.vrabel@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=xen-devel@lists.xenproject.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.