[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [xen-unstable test] 35257: regressions - FAIL

To: Jim Fehlig <jfehlig@xxxxxxxx>
From: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Date: Mon, 2 Mar 2015 11:14:02 +0000
Cc: "xen.org" <Ian.Jackson@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Wei Liu <wei.liu2@xxxxxxxxxx>, Ian Campbell <ian.campbell@xxxxxxxxxx>
Delivery-date: Mon, 02 Mar 2015 11:14:08 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

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.

If we were more clever, osstest would collect corefiles.

Ian.

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

Follow-Ups:
- Re: [Xen-devel] [xen-unstable test] 35257: regressions - FAIL
  - From: Ian Campbell

Prev by Date: Re: [Xen-devel] [PATCH 2/2] xen: arm: Warn if timer interrupts are not level triggered
Next by Date: Re: [Xen-devel] [PATCH] stubdom: fix make clean and distclean on a freshly cloned tree
Previous by thread: Re: [Xen-devel] [xen-unstable test] 35257: regressions - FAIL
Next by thread: Re: [Xen-devel] [xen-unstable test] 35257: regressions - FAIL
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.