From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Jim Fehlig <jfehlig@suse.com>,
xen-devel@lists.xensource.com, Wei Liu <wei.liu2@citrix.com>
Subject: Re: [xen-unstable test] 35257: regressions - FAIL
Date: Mon, 2 Mar 2015 11:38:08 +0000 [thread overview]
Message-ID: <1425296288.1886.37.camel@citrix.com> (raw)
In-Reply-To: <21748.17914.317136.91748@mariner.uk.xensource.com>
On Mon, 2015-03-02 at 11:14 +0000, Ian Jackson wrote:
> Jim Fehlig writes ("Re: [Xen-devel] [xen-unstable test] 35257: regressions - FAIL"):
> ...
> > In my experience, if ERROR is insufficient, INFO and WARNING don't
> > help. DEBUG is needed.
>
> Where does virtd's stderr go ? That is where any assertion failure
> message would be written.
/dev/null from the looks of the code:
http://libvirt.org/git/?p=libvirt.git;a=blob;f=daemon/libvirtd.c;h=2366d63cd3c70f75df5af82d2c241df163293eab;hb=HEAD#l174
Ian
next prev parent reply other threads:[~2015-03-02 11:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 20:14 [xen-unstable test] 35257: regressions - FAIL xen.org
2015-02-27 9:42 ` Ian Campbell
2015-02-27 10:48 ` Wei Liu
2015-02-27 13:13 ` Ian Campbell
2015-02-27 20:47 ` Jim Fehlig
2015-03-02 10:04 ` [PATCH] ts-xen-install: Enable debug level logging in libvirt Ian Campbell
2015-03-02 11:06 ` Ian Jackson
2015-03-02 11:33 ` [PATCH v2] " Ian Campbell
2015-03-02 11:37 ` Ian Jackson
2015-03-02 11:45 ` Ian Campbell
2015-03-03 10:22 ` [PATCH v3] " Ian Campbell
2015-03-03 11:25 ` Ian Campbell
2015-03-02 10:05 ` [xen-unstable test] 35257: regressions - FAIL Ian Campbell
2015-03-02 11:14 ` Ian Jackson
2015-03-02 11:38 ` Ian Campbell [this message]
2015-03-02 17:59 ` Jim Fehlig
2015-03-03 10:37 ` Ian Campbell
2015-02-27 18:51 ` Jim Fehlig
2015-02-27 20:20 ` [libvirt] [Xen-devel] " Ian Campbell
2015-03-03 12:44 ` Ian Campbell
2015-03-03 12:46 ` 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=1425296288.1886.37.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=jfehlig@suse.com \
--cc=wei.liu2@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 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.