33 messages in com.perforce.perforce-user[p4] Perforce Sync does not always wo...
FromSent OnAttachments
Jeremy Russell26 Jul 2000 10:25 
Dave Lewis26 Jul 2000 10:46 
Ed Mack26 Jul 2000 10:54 
Rob Jellinghaus26 Jul 2000 10:56 
Frank Merrow26 Jul 2000 10:57 
Ines Heinz26 Jul 2000 11:09 
Jeremy Russell26 Jul 2000 11:09 
Rick Macdonald26 Jul 2000 11:09 
Dave Lewis26 Jul 2000 11:21 
Marc S. Gibian26 Jul 2000 11:23 
tsh...@cisco.com26 Jul 2000 11:24 
Rick Macdonald26 Jul 2000 11:34 
Jeremy Russell26 Jul 2000 11:34 
Steve Cogorno26 Jul 2000 11:43 
tsh...@cisco.com26 Jul 2000 11:43 
Jeremy Russell26 Jul 2000 11:52 
Jeremy Russell26 Jul 2000 11:53 
Jeremy Russell26 Jul 2000 11:54 
Dave Lewis26 Jul 2000 11:59 
tsh...@cisco.com26 Jul 2000 12:13 
tsh...@cisco.com26 Jul 2000 12:20 
Richard Geiger26 Jul 2000 12:29 
Paul Goffin26 Jul 2000 12:44 
Jeremy Russell26 Jul 2000 12:56 
Boleslaw Ciesielski26 Jul 2000 13:30 
Viktor Haag27 Jul 2000 08:54 
Jo Woodison27 Jul 2000 09:24 
Ed Mack27 Jul 2000 11:12 
Jo Woodison27 Jul 2000 12:11 
Ed Mack27 Jul 2000 12:51 
Viktor Haag27 Jul 2000 13:48 
Viktor Haag27 Jul 2000 13:52 
Viktor Haag27 Jul 2000 13:54 
Subject:[p4] Perforce Sync does not always work...
From:Jeremy Russell (jrus@channelpoint.com)
Date:07/26/2000 11:09:56 AM
List:com.perforce.perforce-user

The entire client spec is simple and looks like this: //depot/tree/... //jrussel/k:/depot/tree/...

A one line client spec shouldn't have these issues.

Other people in the group have spoken with tech support to no avail from my understanding.

Additionally, as per Rob Jellinghaus' response, the directory structure may be huge, but no directory has over 200 files. Also, we don't ever really "touch" these files other than in a read operation so it is not a change of permission problem that you sometimes encounter with p4 sync.

These are machine specific specs that no one else uses due to a very unique structure on our code build machines. We do update the client spec each time before we run, but that should not cause an intermittent problem where only some of the changes are brought over.

I actually have one machine in which the client spec has never changed, and I still cannot get all the changed files every time. More information: this tree is strictly populated through integrate commands as it is the parent tree.

Could updating the client spec be causing these problems? I would hope not since the only thing being changed a majority of the time is the description.

-Jeremy

-----Original Message----- From: Ed Mack [mailto:edm at wrq.com] Sent: Wednesday, July 26, 2000 11:54 AM To: 'Jeremy Russell'; 'perforce-user at perforce.com' Subject: RE: [p4] Perforce Sync does not always work...

What does your clientspec look like? What does Perforce Tech. Support have to say about it? The only problems we have ever had with syncs were due to overlapping client mappings (which was our problem, not Perforce's).

-----Original Message----- From: Jeremy Russell [mailto:jrussel at channelpoint.com] Sent: Wednesday, July 26, 2000 10:26 AM To: 'perforce-user at perforce.com' Subject: [p4] Perforce Sync does not always work...

I am continually frustrated by the fact that "p4 sync //depot/tree/dir/..." does not always sync all the changed files. In order to be sure that I will be syncing all the changed files I am very often forced to add the "-f" option to the sync and do an entire bring over to be sure that I have gotten all the changes.

This is very frustrating because of the code build times we encounter. At this time, because we cannot trust "p4 sync" to bring over every changed files, so we sync an entire code line from Perforce each time we do a build, meaning that 40% to 50% of build time is because of syncing. Additionally, these syncs are between the range of 20,000 to 30,000 files and 100's of MB.

We are working on some solutions involving keeping track of change lists and syncing a range of change lists instead of file specs, but this does not solve the basic issue that "p4 sync" does not work.

I am wondering if anyone else out there has similar issues with "p4 sync" and what you do to deal with it.

Jeremy Russell Release Engineering ChannelPoint, Inc jrussel at channelpoint.com 719.867.9520 AOL\IM jrussel21