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

RE: [Xen-devel] Is the repository broken?

Looks like it's back now. I've got a bunch of Xen-changelog emails, and
checked the xenbits. The tip is:

78 minutes ago: Temporary workaround to xend start problem.  
changeset 7468: 17a9f111fa93 
parent 7467: 2d5b92e7c79a 
tag: tip 
author: jrb44@xxxxxxxxxxxxxxxxx 
date: Fri Oct 21 17:51:42 2005 
files: tools/python/xen/util/process.py tools/python/xen/xend/Vifctl.py

Intel Open Source Technology Center 

-----Original Message-----
From: Nivedita Singhvi [mailto:niv@xxxxxxxxxx] 
Sent: Friday, October 21, 2005 9:49 AM
To: Nakajima, Jun
Cc: David F Barrera; Burns, Bill; xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Is the repository broken?

Nakajima, Jun wrote:
> David F Barrera wrote:
>>I saw the same thing. I just assumed that there had not been any
>>checkins since yesterday.
> This is basically what I memntioned in the previous email:
> Nakajima, Jun wrote:
>>I heard "the mini-regression test now in place between a staging tree
>>and the public tree currently fails on some 64bit SMP cases and
>>therefore all patches submitted after are still queued up in the
>>staging tree."
>>I'm wondering how we can resolve that kind of situation effectively:
>>- Can we get the results from mini-regression tests?
>>- Can we access the staging tree to tell if the patch sent out has
>>been accepted or not? We need to reproduce the tree and problem to
>>fix the bug.


Is that what's going on? How can we help?

Is there a fifo operation in place? Can we perhaps remove
patches which fail and debug/process offline, perhaps post
to list and get testing, etc? Continue with regression
testing remaining queue?


Xen-devel mailing list



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