What happened?

What happened?

[David_Wolinsky]

[-- Attachment #1.1: Type: text/plain, Size: 302 bytes --]

What happened to xenbits... After change set 5792, it seems to be time
retarded... what's the possibility of something like this breaking Xen?
I ask, because I had a stable system and now its back to the state is
was a week ago... (I am only sshed in so I can't give more detailed
info).

David

[-- Attachment #1.2: Type: text/html, Size: 720 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: What happened?

[Keir Fraser]

On 17 Jul 2005, at 14:33, <David_Wolinsky@Dell.com> wrote:

> What happened to xenbits… After change set 5792, it seems to be time 
> retarded… what's the possibility of something like this breaking Xen?  
> I ask, because I had a stable system and now its back to the state is 
> was a week ago… (I am only sshed in so I can't give more detailed 
> info).

There doesn't appear to be anything wrong with xenbits. I just cloned a 
fresh copy of it and it looks up to date.

If you pull new changesets into an existing local repository, you do 
need to 'hg update' to make your check-out copy match the latest 
version.

  -- Keir

Re: What happened?

[James Bulpin]

The other thing to watch out for is the history (hg history and web 
interface) is ordered by the date the changeset was applied to the 
repository in question rather than when it was first checked into a 
repository (the latter being the date field in the history). Changesets 
5792 to 5804 were made to the IA64 tree a while ago. They were merged 
with the main tree on Friday which is why you see a break in the date 
ordering.

James

Keir Fraser wrote:
> 
> On 17 Jul 2005, at 14:33, <David_Wolinsky@Dell.com> wrote:
> 
>> What happened to xenbits… After change set 5792, it seems to be time 
>> retarded… what's the possibility of something like this breaking Xen?  
>> I ask, because I had a stable system and now its back to the state is 
>> was a week ago… (I am only sshed in so I can't give more detailed info).
> 
> 
> There doesn't appear to be anything wrong with xenbits. I just cloned a 
> fresh copy of it and it looks up to date.
> 
> If you pull new changesets into an existing local repository, you do 
> need to 'hg update' to make your check-out copy match the latest version.
> 
>  -- Keir
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

RE: What happened?

[David_Wolinsky]

What's the possibility a merge would break something?  I had some severe
instability a few weeks back, middle of last week it was fine, then I
did an update after IA64 tree was merged and it started crashing.  I
have just started trying to figure out the problem, but I'm trying to
rule out the noticeable things first.

David 

-----Original Message-----
From: James Bulpin [mailto:james@xensource.com] 
Sent: Sunday, July 17, 2005 3:11 PM
To: Keir Fraser
Cc: Wolinsky, David; xen-devel@lists.xensource.com
Subject: Re: [Xen-devel] What happened?

The other thing to watch out for is the history (hg history and web
interface) is ordered by the date the changeset was applied to the
repository in question rather than when it was first checked into a
repository (the latter being the date field in the history). Changesets
5792 to 5804 were made to the IA64 tree a while ago. They were merged
with the main tree on Friday which is why you see a break in the date
ordering.

James

Keir Fraser wrote:
> 
> On 17 Jul 2005, at 14:33, <David_Wolinsky@Dell.com> wrote:
> 
>> What happened to xenbits... After change set 5792, it seems to be
time 
>> retarded... what's the possibility of something like this breaking
Xen?  
>> I ask, because I had a stable system and now its back to the state is

>> was a week ago... (I am only sshed in so I can't give more detailed
info).
> 
> 
> There doesn't appear to be anything wrong with xenbits. I just cloned
a 
> fresh copy of it and it looks up to date.
> 
> If you pull new changesets into an existing local repository, you do 
> need to 'hg update' to make your check-out copy match the latest
version.
> 
>  -- Keir
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

Re: What happened?

[Keir Fraser]

On 17 Jul 2005, at 21:58, <David_Wolinsky@Dell.com> wrote:

> What's the possibility a merge would break something?  I had some 
> severe
> instability a few weeks back, middle of last week it was fine, then I
> did an update after IA64 tree was merged and it started crashing.  I
> have just started trying to figure out the problem, but I'm trying to
> rule out the noticeable things first.

We are pretty sure there's a nasty memory-trashing bug in the unstable 
tree, that hasn't been fixed yet. It may come and go for you according 
to phase of the moon etc. I don't have 100% trust in mercurial yet, but 
I'm pretty sure its merging is not to blame here.

  -- Keir

RE: What happened?

[David_Wolinsky]

Thanks for the info, if there is anything I or the community can do to
help trace it down, please respond with details.

Thanks,
David 

-----Original Message-----
From: Keir Fraser [mailto:Keir.Fraser@cl.cam.ac.uk] 
Sent: Monday, July 18, 2005 2:44 AM
To: Wolinsky, David
Cc: james@xensource.com; xen-devel@lists.xensource.com
Subject: Re: [Xen-devel] What happened?


On 17 Jul 2005, at 21:58, <David_Wolinsky@Dell.com> wrote:

> What's the possibility a merge would break something?  I had some 
> severe instability a few weeks back, middle of last week it was fine, 
> then I did an update after IA64 tree was merged and it started 
> crashing.  I have just started trying to figure out the problem, but 
> I'm trying to rule out the noticeable things first.

We are pretty sure there's a nasty memory-trashing bug in the unstable
tree, that hasn't been fixed yet. It may come and go for you according
to phase of the moon etc. I don't have 100% trust in mercurial yet, but
I'm pretty sure its merging is not to blame here.

  -- Keir