xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>, Doug Goldstein <cardoe@cardoe.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>, osstest-admin@xenproject.org
Subject: Re: [xen-unstable test] 77945: regressions - FAIL
Date: Thu, 14 Jan 2016 13:57:04 +0000	[thread overview]
Message-ID: <1452779824.2185.37.camel@citrix.com> (raw)
In-Reply-To: <5697A78902000078000C6BAA@prv-mh.provo.novell.com>

On Thu, 2016-01-14 at 05:50 -0700, Jan Beulich wrote:
> > > > On 14.01.16 at 12:42, <ian.campbell@citrix.com> wrote:
> > The bisector is working:
> > http://logs.test-lab.xenproject.org/osstest/results/bisect/xen-unstable
> > /test 
> > -amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm.xen-install.html
> > 
> > and has gotten to this range:
> > 
> >     $ git log --oneline 5513bd0b4675..20c8f1a8a5fd
> >     20c8f1a convert XSM_ENABLE to Kconfig
> >     529298f convert FLASK_ENABLE to Kconfig
> >     361b4f9 build: save generated xen .config
> >     e3cce17 x86/VPMU: implement ipc and arch filter flags
> > 
> > I suspect the issue is that 529298f removes FLASK_ENABLE from the top-
> > level, but that is used in tools/Makefile. i.e. there is that other
> > patch
> > which needed to go before the two included above.
> 
> And is that other patch ready to go in? If not, do we need to
> revert another time?

I think that is likely to be the case, yes.

> In any event - Doug, you should point out such dependencies in
> the submission, e.g. after the first --- marker.

Really they should have been in the same series in this case.

Ian.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2016-01-14 13:57 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-14 14:58 [OSSTEST PATCH] enable FLASK_ENABLE when using it for testing Doug Goldstein
2016-01-14 14:28 ` [OSSTEST PATCH] pass --{enable, disable}-xsmpolicy based on XSM state Doug Goldstein
2016-01-13 19:30   ` [xen-unstable test] 77945: regressions - FAIL osstest service owner
2016-01-14  9:30     ` Jan Beulich
2016-01-14 11:42       ` Ian Campbell
2016-01-14 12:50         ` Jan Beulich
2016-01-14 13:57           ` Ian Campbell [this message]
2016-01-14 14:07             ` Doug Goldstein
2016-01-14 14:44               ` Ian Campbell
2016-01-14 14:54                 ` Doug Goldstein
2016-01-14 14:48               ` Jan Beulich
2016-01-14 15:04                 ` Doug Goldstein
2016-01-14 16:27             ` [xen-unstable test] 77945: regressions - FAIL [and 2 more messages] Ian Jackson
2016-01-14 17:07               ` Doug Goldstein
2016-01-14 17:18                 ` Ian Jackson
2016-01-14 17:25                   ` Ian Campbell
2016-01-14 19:10                   ` Doug Goldstein
2016-01-15 16:06               ` Jan Beulich
2016-01-15 17:06               ` Ian Campbell
2016-01-15 17:10                 ` Ian Jackson
2016-01-15 17:15                 ` Jan Beulich
2016-01-15 17:24                   ` Andrew Cooper
2016-01-15 17:42                     ` Ian Campbell
2016-01-18  7:49                       ` Jan Beulich
2016-01-18  8:55                         ` Andrew Cooper
2016-01-18  9:41                         ` Ian Campbell
2016-01-18  9:47                           ` Jan Beulich
2016-01-18 11:22                             ` Ian Campbell
2016-01-18 11:28                               ` Ian Jackson
2016-01-18 11:36                                 ` Ian Campbell
2016-01-18 12:09                                   ` Ian Campbell
2016-01-15 17:21                 ` Doug Goldstein
2016-01-14 21:40   ` [OSSTEST PATCH] pass --{enable, disable}-xsmpolicy based on XSM state Doug Goldstein
2016-01-16 20:50   ` Doug Goldstein
2016-01-14 16:22 ` [OSSTEST PATCH] enable FLASK_ENABLE when using it for testing Ian Campbell
2016-01-14 16:34   ` Doug Goldstein
2016-01-16 20:54 ` Doug Goldstein

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=1452779824.2185.37.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=cardoe@cardoe.com \
    --cc=osstest-admin@xenproject.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).