xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
	xen-devel@lists.xensource.com,
	Paul Durrant <paul.durrant@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	osstest service owner <osstest-admin@xenproject.org>
Subject: Re: [qemu-mainline test] 80469: regressions - FAIL
Date: Wed, 10 Feb 2016 12:17:40 +0000	[thread overview]
Message-ID: <1455106660.19857.157.camel@citrix.com> (raw)
In-Reply-To: <1455105806.19857.156.camel@citrix.com>

On Wed, 2016-02-10 at 12:03 +0000, Ian Campbell wrote:
> On Wed, 2016-02-10 at 11:53 +0000, Stefano Stabellini wrote:
> > On Wed, 10 Feb 2016, Ian Campbell wrote:
> > > Adding some CCs. 
> > > 
> > > On Fri, 2016-02-05 at 11:52 +0000, Anthony PERARD wrote:
> > > > On Fri, Feb 05, 2016 at 06:30:25AM +0000, osstest service owner
> > > > wrote:
> > > > > flight 80469 qemu-mainline real [real]
> > > > > http://logs.test-lab.xenproject.org/osstest/logs/80469/
> > > > > 
> > > > > Regressions :-(
> > > > > 
> > > > > Tests which did not succeed and are blocking,
> > > > > including tests which could not be run:
> > > > >  build-i386                    5 xen-build                 fail
> > > > > REGR. vs. 79947
> > > > >  build-amd64                   5 xen-build                 fail
> > > > > REGR. vs. 79947
> > > > >  build-i386-xsm                5 xen-build                 fail
> > > > > REGR. vs. 79947
> > > > >  build-amd64-xsm               5 xen-build                 fail
> > > > > REGR. vs. 79947
> > > > >  build-armhf                   5 xen-build                 fail
> > > > > REGR. vs. 79947
> > > > >  build-armhf-xsm               5 xen-build                 fail
> > > > > REGR. vs. 79947
> > > > 
> > > > ./configure of QEMU fail with:
> > > > "ERROR: invalid trace backends
> > > >         Please choose supported trace backends."
> > > > 
> > > > They have remove the "stderr" tracebackend, and replaced it by
> > > > "log".
> > > > Which
> > > > also became the default. I have not look at what to do yet, but the
> > > > configure
> > > > option "--enable-trace-backend=stderr" as became invalid.
> > > 
> > > Paul added this IIRC.
> > > 
> > > If it isn't immediately obvious what an appropriate replacement is
> > > (which
> > > remember needs to work with at least qemu-xen-unstable as well as
> > > qemu-
> > > upstream) then I think we should just remove this option from
> > > xen.git/tools/Makefile for the time being.
> > > 
> > > FWIW the bisector has fingered:
> > > 
> > >   commit ed7f5f1d8db06fc31352a5ef4f54985e630c575a
> > >   Author: Paolo Bonzini <pbonzini@redhat.com>
> > >   Date:   Thu Jan 7 16:55:30 2016 +0300
> > >   
> > >       trace: convert stderr backend to log
> > >       
> > >       [Also update .travis.yml --enable-trace-backends=stderr
> > >       --Stefan]
> > >       
> > >       Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> > >       Signed-off-by: Denis V. Lunev <den@openvz.org>
> > >       Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
> > >       Message-id: 1452174932-28657-10-git-send-email-den@openvz.org
> > >       Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> > > 
> > > It looks like s/stderr/log/g would work with qemu-mainline, but we'd
> > > need
> > > that backported to qemu-xen-unstable too.
> > > 
> > > Or given:
> > >     git show --stat -M ed7f5f1d8db06fc31352a5ef4f54985e630c575a
> > >     [...]
> > >      scripts/tracetool/backend/{stderr.py => log.py} |  9 +++++----
> > > 
> > > Maybe xen.git/tools/Makefile could probe for the presence of these
> > > files?
> >  
> > We can have QEMU list the trace backends available with:
> > 
> > ./scripts/tracetool.py --list-backends
> > 
> > that works on all qemu-xen versions >= 4.3.
> > 
> > Same output:
> 
> Sample?
> 
> > nop, ust, stderr, dtrace, simple
> 
> Here (QEMU  master) it is:
>     nop, dtrace, ftrace, log, simple, ust
> 
> Who is going to produce a patch to use this?

Actually, I've just coincidentally tripped over this in what I'm looking at
now, so I suppose I'll whip something up.

Ian.


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

  reply	other threads:[~2016-02-10 12:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-05  6:30 [qemu-mainline test] 80469: regressions - FAIL osstest service owner
2016-02-05 11:52 ` Anthony PERARD
2016-02-10 10:14   ` Ian Campbell
2016-02-10 11:53     ` Stefano Stabellini
2016-02-10 12:03       ` Ian Campbell
2016-02-10 12:17         ` Ian Campbell [this message]
2016-02-10 12:09     ` Paul Durrant
2016-02-10 15:24       ` Ian Campbell
2016-02-10 16:31         ` Paul Durrant

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=1455106660.19857.157.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=osstest-admin@xenproject.org \
    --cc=paul.durrant@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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).