From mboxrd@z Thu Jan  1 00:00:00 1970
From: George Dunlap <george.dunlap@eu.citrix.com>
Subject: Re: [xen-unstable test] 17180: regressions - trouble:
	broken/fail/pass
Date: Fri, 8 Mar 2013 14:34:45 +0000
Message-ID: <5139F705.1020908@eu.citrix.com>
References: <osstest-17180-mainreport@xen.org>
	<20793.62908.481259.416870@mariner.uk.xensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <20793.62908.481259.416870@mariner.uk.xensource.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

On 08/03/13 14:29, Ian Jackson wrote:
> xen.org writes ("[xen-unstable test] 17180: regressions - trouble: broken/fail/pass"):
>> flight 17180 xen-unstable real [real]
>> http://www.chiark.greenend.org.uk/~xensrcts/logs/17180/
>>
>> Regressions :-(
>>
>> Tests which did not succeed and are blocking,
>> including tests which could not be run:
>>   test-amd64-i386-xl-credit2    5 xen-boot             fail REGR. vs. 16772
> Mar  8 09:36:01.369651 (XEN) ****************************************
> Mar  8 09:36:01.377561 (XEN) Panic on CPU 0:
> Mar  8 09:36:01.377601 (XEN) Assertion 'rt_credit >= 0' failed at sched_credit2.c:1559
> Mar  8 09:36:01.377657 (XEN) ****************************************
> Mar  8 09:36:01.385966 (XEN)
> Mar  8 09:36:01.386001 (XEN) Reboot in five seconds...
>
> No stack trace for some reason.  I guess this is probably related to
> c0704a8a or 8b3072a0.

Yes, Jan brought this to my attention yesterday; I've just posted a 
patch series fixing it, which Jan has some minor comments on.  Would you 
like me to cc you on the resend?

  -George