Jump to content


RCS delta mangled: empty!


  • Please log in to reply
5 replies to this topic

#1 David Yerkess

David Yerkess

    Advanced Member

  • Members
  • PipPipPip
  • 78 posts

Posted 25 July 2013 - 10:57 AM

We are evaluating Perforce and I am stuck with an error that keeps occurring:

Operation 'dm-SubmitFile' failed.
Librarian checkin f:/perforce/some_rather_long_path/sign_d.tga failed.
RCS checkin C:\Windows\TEMP\t2656t498316.tmp#1.285 failed!
RCS delta mangled: empty!

I am getting this error when running a C# program with P4API.NET.

The C# program (made only to test the API) gets a list of file names from a live project we have and creates a text file with the same name for each file.
Within the files it writes the text 'Change 1'.
These files (96k) are then added to a changelist and submitted.

Each time I try to repeat the process, the file that fails changes.
If I try to submit the file that failed by moving it to a new changelist (using P4V), then it submits without problems.
Out of the 96k files only one seems to fail.

Seeing I have been repeating this process on the same Depot, could it be connected to the fact that I am deleting all the files and then re-adding them?
Something else I might be doing wrong?

Thanks,
David.

#2 P4Matt

P4Matt

    Advanced Member

  • Members
  • PipPipPip
  • 1383 posts

Posted 25 July 2013 - 07:14 PM

If you do the entire submit from P4V does it work? I'd like to remove the API from the equation. Are the files empty or do they have content? At first blush everything seems copacetic.

#3 David Yerkess

David Yerkess

    Advanced Member

  • Members
  • PipPipPip
  • 78 posts

Posted 25 July 2013 - 08:37 PM

All files contain the text 'Change 1'.

I tried again in the same Depot, but to a new path so that there were no previous revisions. 96.375 files were submitted in the changelist without problems.
The C# program then continues by editing a subset of files chosen randomly. This changelist of 48.197 edited files (added text 'Change 2') failed with the same problem.
I tried to submit the pending changelist from P4V, but each time it fails on a different file.Here is the log from within P4V:

p4 submit -f submitunchanged -i
2 errors reported
Operation 'dm-SubmitFile' failed.
Librarian checkin f:/perforce/some_rather_long_path/caboutbox.designer.cs failed.
RCS checkin C:\Windows\TEMP\t3608t532527.tmp#1.293 failed!
RCS delta mangled: empty!
Submit aborted -- fix problems then use 'p4 submit -c 293'.
Some file(s) could not be transferred from client.
p4 submit -f submitunchanged -i
2 errors reported
Operation 'dm-SubmitFile' failed.
Librarian checkin f:/perforce/some_rather_long_path/splinefile.h failed.
RCS checkin C:\Windows\TEMP\t1608t390908.tmp#1.293 failed!
RCS delta mangled: empty!
Submit aborted -- fix problems then use 'p4 submit -c 293'.
Some file(s) could not be transferred from client.
p4 submit -f submitunchanged -i
2 errors reported
Operation 'dm-SubmitFile' failed.
Librarian checkin f:/perforce/some_rather_long_path/engrabber.h failed.
RCS checkin C:\Windows\TEMP\t2612t352082.tmp#1.293 failed!
RCS delta mangled: empty!
Submit aborted -- fix problems then use 'p4 submit -c 293'.
Some file(s) could not be transferred from client.

Note: the paths are edited, because I cannot show them publicly.

Here is the content on one of the failed files in the depot:


head 1.293;
access ;
symbols ;
locks ;comment @@;


1.293
date 2013.07.25.18.56.19; author p4; state Exp;
branches ;
next 1.292;

1.292
date 2013.07.25.17.41.02; author p4; state Exp;
branches ;
next ;


desc
@@


1.293
log
@@
text
@25/07/2013 17:33:14 - This is change 1
25/07/2013 17:45:26 - This is change 2
@


1.292
log
@@
text
@d2 1
@

Changelist 293 is the changelist that is still pending.
Is it normal that the changes are added before submit is successful?

#4 P4Matt

P4Matt

    Advanced Member

  • Members
  • PipPipPip
  • 1383 posts

Posted 25 July 2013 - 08:46 PM

No, something really terrible is happening. You have full access to support@perforce.com as an evaluating user. I'd highly recommend contacting them; I suspect seeing your full logs will be important for solving this problem.

I searched our issue tracker and then only job that matches up is something with a much older release that has been verified as fixed many times over. I'm happy to help you here, but I think support is your best bet for getting to the bottom of this.

#5 David Yerkess

David Yerkess

    Advanced Member

  • Members
  • PipPipPip
  • 78 posts

Posted 25 July 2013 - 09:01 PM

Wow, a very quick response! :)
We don't have an official evaluation, but at the moment are using the 20 user version.
Can I contact support anyway? Otherwise I will wait until we actually request a proper evaluation.

Thanks!

#6 P4Matt

P4Matt

    Advanced Member

  • Members
  • PipPipPip
  • 1383 posts

Posted 25 July 2013 - 09:44 PM

Yuppers. 20/20 version gets support.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users