Is the repository broken?

Is the repository broken?

[Burns, Bill]

The last pull that got me anything was on Oct 20
and the last changeset is:

changeset:   7425:7c951e3eb5ab
tag:         tip
user:        emellor@leeni.uk.xensource.com
date:        Wed Oct 19 06:53:00 2005 +0100
summary:     Remove unused parameter from addControllerClass.  This
became unuse
d when the


I see more going by on the list. The web interface to
the repository shows the same tip.

Thanks,
 Bill Burns

Re: Is the repository broken?

[David F Barrera]

I saw the same thing. I just assumed that there had not been any 
checkins since yesterday.

David

Burns, Bill wrote:

>The last pull that got me anything was on Oct 20
>and the last changeset is:
>
>changeset:   7425:7c951e3eb5ab
>tag:         tip
>user:        emellor@leeni.uk.xensource.com
>date:        Wed Oct 19 06:53:00 2005 +0100
>summary:     Remove unused parameter from addControllerClass.  This
>became unuse
>d when the
>
>
>I see more going by on the list. The web interface to
>the repository shows the same tip.
>
>Thanks,
> Bill Burns
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
>
>  
>

RE: Is the repository broken?

[Nakajima, Jun]

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.
> 
> Jun
> ---
> Intel Open Source Technology Center


> 
> David
> 
> Burns, Bill wrote:
> 
>> The last pull that got me anything was on Oct 20
>> and the last changeset is:
>> 
>> changeset:   7425:7c951e3eb5ab
>> tag:         tip
>> user:        emellor@leeni.uk.xensource.com
>> date:        Wed Oct 19 06:53:00 2005 +0100
>> summary:     Remove unused parameter from addControllerClass.  This
>> became unuse d when the
>> 
>> 
>> I see more going by on the list. The web interface to
>> the repository shows the same tip.
>> 
>> Thanks,
>> Bill Burns
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>> 
>> 
>> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel



Jun
---
Intel Open Source Technology Center

Re: Is the repository broken?

[Nivedita Singhvi]

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.
>>

Hello,

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?

thanks,
Nivedita

RE: Is the repository broken?

[Nakajima, Jun]

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@plym.cl.cam.ac.uk 
date: Fri Oct 21 17:51:42 2005 
files: tools/python/xen/util/process.py tools/python/xen/xend/Vifctl.py


Jun
---
Intel Open Source Technology Center 

-----Original Message-----
From: Nivedita Singhvi [mailto:niv@us.ibm.com] 
Sent: Friday, October 21, 2005 9:49 AM
To: Nakajima, Jun
Cc: David F Barrera; Burns, Bill; xen-devel@lists.xensource.com
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.
>>

Hello,

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?

thanks,
Nivedita