[p4] P4EXP 2005.2

[Jeff Jensen]

Hi Greg,

Thank you for sharing this issue...it explains what I saw the other week and
absolutely could not explain it (I was working with someone somewhat new to
branching and Perforce; you can imagine how well that went over!)

Do you have a call number to share, so those that have experienced it can
join it?


FWIW, I have seen not problems with 2005.2 other than this issue.


-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Whitfield, Greg
Sent: Thursday, February 09, 2006 3:18 PM
To: Jamison, Shawn; Leo Zelevinsky
Cc: Zarnes, Todd; perforce-user at perforce.com
Subject: Re: [p4] P4EXP 2005.2

I missed the workaround out of my previous email:

- Integrate and resolve as normal (auto resolve can be either safe or not -
the bug occurs with both -am and -as options)
- Compile locally. If you get compile errors and a look at the file causing
the errors shows a screwed up integration, then revert just that file.
- Integrate the single file again.
- Resolve, but do an "accept theirs". 

You have to hope that the corruption is picked up by a failed compilation -
chances are it will be. And then resist the temptation to edit the file. The
revert->reintegrate->accept theirs will then do the trick.

Also note that this does not appear to work for per-changelist integrations.

Greg
~~~~

-----Original Message-----
From: Jamison, Shawn [mailto:sjamison at ciena.com]
Sent: 09 February 2006 20:51
To: Whitfield, Greg; Leo Zelevinsky
Cc: Zarnes, Todd; perforce-user at perforce.com
Subject: RE: [p4] P4EXP 2005.2

I just got nailed by this very issue but not with P4EXP but with P4WIN
2005.2 server and 2005.2 clients.

Does a sync after the submit clean up the workspace?
Is there a workaround?  

-Shawn J>


-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com]On Behalf Of Whitfield, Greg
Sent: Thursday, February 09, 2006 11:42 AM
To: Leo Zelevinsky
Cc: Zarnes, Todd; perforce-user at perforce.com
Subject: Re: [p4] P4EXP 2005.2


The big one is a merge/integration bug that causes corrupted files when you
auto merge some files where the only changes are on "theirs". The merge
corrupts the local client copy. If the user just submits, the local copy
stays corrupted but the server file is OK due to the lazy copy mechanism.
When first reported to me I just did not believe it

However - and this is the killer - if the user does notice, often by a
failed compilation, and then attempts to edit the file after the merge and
before submission, the version that gets submitted is corrupted. 

The odd thing is that not all files show this behaviour - just some. By
"corrupted" we get seemingly random symbol deletions and additions in the
files being merged. 

Note that Perforce support are actively looking at this, and have managed to
repeat it. I just don't yet have a fix date.

They supplied a procedural work-around, but that does not work in the case
of individual change list integrations.

Apart from that we have an odd verify error introduced by the server update
- also being looked at by support. There's a related memory concern, but I
think that has been reported in another thread, and maybe a case of a change
in behaviour rather than a bug.

We also had a bug in P4Win (2005.2.90475) with reverted integrations, but
this was fixed by a new release on Jan 19th (2005.2.91908).
Although, interestingly, Perforce's download page did not appear to report
the later version - this may since have been updated.

And, while not really a bug, or even 2005.2, I really wish P4Win was in the
main installer - this change has been an administrative niggle, where users
with old versions only install "Perforce.exe", and so end up still using old
P4Win's.

God, this sounds like a giant moan!  It's really not meant to be - Perforce
support have been their usual helpful selves and the only critical issue is
the integration bug. I'm sure they'll fix it soon - hopefully before my
users lynch me!

We're on Windows XP Server for P4s, and 95% of clients are WinXP based.

BTW, my recommendation to not upgrade is purely a personal one borne out of
the above, and in no way reflects the views of my company.

Greg
~~~~


-----Original Message-----
From: leo.zelevinsky at gmail.com [mailto:leo.zelevinsky at gmail.com] On Behalf
Of Leo Zelevinsky
Sent: 09 February 2006 16:05
To: Whitfield, Greg
Cc: Zarnes, Todd; perforce-user at perforce.com
Subject: Re: [p4] P4EXP 2005.2

Would you mind listing some of these issues? We are considering upgrading
shortly and I'm disturbed by your statement.

Also - are we talking about server or client performance?

Thanks!

On 2/9/06, Whitfield, Greg <gwhitfield at europe.ea.com> wrote:
> I have had reports from a few of my users that things do appear slower

> since the upgrade, to the extent that uninstalling that component has 
> sometimes been necessary.
>
> We are experiencing a number of issues with 2005.2 that we did not 
> have with 2005.1. I would not recommend the upgrade.
>
> Greg
> ~~~~
>
>
> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Zarnes, Todd
> Sent: 09 February 2006 01:16
> To: perforce-user at perforce.com
> Subject: [p4] P4EXP 2005.2
>
> Anybody else seeing a slow down in Performance with the new 2005.2 
> P4EXP?
>
>
>
> Todd  Zarnes
>
> Intuit Eclipse SCM
>
> 303.938.8801 x1544
>
>
>
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com 
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com 
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>

_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user

_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user