Jump to content


"Submit aborted" - perforce refuses to submit large chunks of changes at once.

Unreal engine

  • Please log in to reply
13 replies to this topic

#1 Araklaj

Araklaj

    Newbie

  • Members
  • Pip
  • 5 posts

Posted 17 October 2016 - 07:55 AM


I am using P4V for my game project in Unreal Engine. For whatever reason, trying to submit a larger amount of various changes at once, say materials + maps + meshes sometimes results in the unhelpful "Submit aborted" error in perforce P4V visual client. If I submit the same content in smaller chunks, say materials first, then meshes, then sub-levels, then main level.. It all works.

What on earth could be causing this behavior? Only thing I can think of is some weird "dependency" system that prevents certain files being submitted before the assets they rely on are already in the repo. This seems to occur when trying to submit levels and assets at same time, or submitting main level + its sublevels at the same time. The weird thing is, however, is that this behavior started just recently, I had no issues submitting a day's work before.


#2 Robert Cowham

Robert Cowham

    Advanced Member

  • PCP
  • 269 posts
  • LocationLondon, UK

Posted 17 October 2016 - 12:19 PM

Could be network or other resource related. Worth checking what error is in server (p4d) logs.
Co-Author of "Learning Perforce SCM", PACKT Publishing, 25 September 2013, ISBN 9781849687645

"It's wonderful to see a new book about Perforce, especially one written by Robert Cowham and Neal Firth. No one can teach Perforce better than these seasoned subject matter experts"
  • Laura Wingerd, author of Practical Perforce, former VP of Product Technology at Perforce

#3 Araklaj

Araklaj

    Newbie

  • Members
  • Pip
  • 5 posts

Posted 18 October 2016 - 11:34 AM

View PostRobert Cowham, on 17 October 2016 - 12:19 PM, said:

Worth checking what error is in server (p4d) logs.

Sorry, where/how can I find those logs, as a user (Im not server admin)? Although I'm not sure if it's a network error, as it depends solely on which files are included at same time.

I enabled logging to file in P4V, but it doesn't say cause of error:

00000000 13:49:29.279 [0x18fd8612090] submit --parallel=threads=4,batch=8,min=9 -f submitunchanged -i
00000000 13:49:30.582 [0x18fd8612090][31051c31] Submit aborted -- fix problems then use 'p4 submit -c 2910'.

This seems to be a pure P4V client issue as I could submit the same batch of files through Unreal's built-in version control without issues.

#4 Mailman Sync

Mailman Sync

    Advanced Member

  • Maillist Aggregator
  • 2495 posts

Posted 18 October 2016 - 01:25 PM

Originally posted to the perforce-user mailing list by: Michael Mirman


Run "p4 configure show P4LOG" - it will show you the path to the p4d log.

--
Michael Mirman
MathWorks, Inc.
3 Apple Hill Drive, Natick, MA 01760
508-647-7555

Quote

-----Original Message-----
[...]

Quote

[http://forums.perfor...dule=forums
tion=findpost&pid=20555]
Robert Cowham, on 2016/10/17 12:19:31 UTC, said:

Quote

   Worth checking what error is in server (p4d) logs.

Sorry, where/how can I find those logs?



--
Please click here to see the post in its original format:
  http://forums.perfor...submit-aborted-
perforce-refuses-to-submit-large-chunks-of-changes-at-once
_______________________________________________
perforce-user mailing list  -  perforce-user@perforce.com
http://maillist.perf...o/perforce-user
_______________________________________________
perforce-user mailing list  -  perforce-user@perforce.com
http://maillist.perf...o/perforce-user




#5 Araklaj

Araklaj

    Newbie

  • Members
  • Pip
  • 5 posts

Posted 18 October 2016 - 06:03 PM

View PostMailman Sync, on 18 October 2016 - 01:25 PM, said:


Run "p4 configure show P4LOG" - it will show you the path to the p4d log.


I am not admin, it says access has not been enabled for my user. But as all other team members seem to not have any issues, it feels to be on my end only.

#6 Mailman Sync

Mailman Sync

    Advanced Member

  • Maillist Aggregator
  • 2495 posts

Posted 18 October 2016 - 06:30 PM

Originally posted to the perforce-user mailing list by: Michael Mirman


If you are not an admin, then knowing the path to the log may not be enough.
In our deployment regular users (not admins) don’t have the access to the p4d logs.

--
Michael Mirman
MathWorks, Inc.
3 Apple Hill Drive, Natick, MA 01760
508-647-7555

Quote

-----Original Message-----
From: perforce-user [mailto:perforce-user-bounces@perforce.com] On
Behalf Of Araklaj
Sent: Tuesday, October 18, 2016 2:05 PM
To: perforce-user@perforce.com
Subject: Re: [p4] "Submit aborted" - perforce refuses to submit large chunks
of changes at once.

Posted on behalf of forum user 'Araklaj'.



[http://forums.perfor...dule=forums
tion=findpost&pid=20569]
Mailman Sync, on 2016/10/18 13:25:10 UTC, said:

Quote


  Run "p4 configure show P4LOG" - it will show you the path to the p4d log.


I am not admin, it says access has not been enabled for my user. But as all
other team members seem to not have any issues, it feels to be on my end
only.



--
Please click here to see the post in its original format:
  http://forums.perfor...submit-aborted-
perforce-refuses-to-submit-large-chunks-of-changes-at-once
_______________________________________________
perforce-user mailing list  -  perforce-user@perforce.com
http://maillist.perf...o/perforce-user
_______________________________________________
perforce-user mailing list  -  perforce-user@perforce.com
http://maillist.perf...o/perforce-user




#7 Sambwise

Sambwise

    Advanced Member

  • Members
  • PipPipPip
  • 782 posts

Posted 18 October 2016 - 06:56 PM

View PostAraklaj, on 18 October 2016 - 11:34 AM, said:

I enabled logging to file in P4V, but it doesn't say cause of error:

00000000 13:49:29.279 [0x18fd8612090] submit --parallel=threads=4,batch=8,min=9 -f submitunchanged -i
00000000 13:49:30.582 [0x18fd8612090][31051c31] Submit aborted -- fix problems then use 'p4 submit -c 2910'.

This seems to be a pure P4V client issue as I could submit the same batch of files through Unreal's built-in version control without issues.

It might be a problem with the --parallel submit option -- see if there's an option in P4V to disable it?  (This has changed across various releases of the client and server so I'm not sure offhand how you might configure it with your particular versions of each.)

#8 p4steph

p4steph

    Member

  • Members
  • PipPip
  • 19 posts

Posted 18 October 2016 - 07:10 PM

This sounds familiar.
Before I left Perforce, I was working on tracking down a similar issue.You should contact Perforce support to report this issue and see if they have a patch for it yet. 

steph



    On Tuesday, October 18, 2016 12:00 PM, Sambwise <perforce-user-forum@forums.perforce.com> wrote:


Posted on behalf of forum user 'Sambwise'.



[http://forums.perfor...post&pid=20564]
Araklaj, on 2016/10/18 11:34:22 UTC, said:

Quote

    I enabled logging to file in P4V, but it doesn't say cause of error:
 
  00000000 13:49:29.279 [0x18fd8612090] submit --parallel=threads=4,batch=8,min=9 -f submitunchanged -i
  00000000 13:49:30.582 [0x18fd8612090][31051c31] Submit aborted -- fix problems then use 'p4 submit -c 2910'.
 
  This seems to be a pure P4V client issue as I could submit the same batch of files through Unreal's built-in version control without issues.
   
It might be a problem with the --parallel submit option -- see if there's an
option in P4V to disable it?�(This has changed across various
releases of the client and server so I'm not sure offhand how you might
configure it with your particular versions of each.)



--
Please click here to see the post in its original format:
  http://forums.perfor...changes-at-once

_______________________________________________
perforce-user mailing list  -  perforce-user@perforce.com
http://maillist.perf...o/perforce-user



_______________________________________________
perforce-user mailing list  -  perforce-user@perforce.com
http://maillist.perf...o/perforce-user



#9 Araklaj

Araklaj

    Newbie

  • Members
  • Pip
  • 5 posts

Posted 21 October 2016 - 09:56 AM

View PostSambwise, on 18 October 2016 - 06:56 PM, said:

It might be a problem with the --parallel submit option -- see if there's an option in P4V to disable it?  (This has changed across various releases of the client and server so I'm not sure offhand how you might configure it with your particular versions of each.)

That seems to have solved the issue! Interesting behavior.

#10 Sambwise

Sambwise

    Advanced Member

  • Members
  • PipPipPip
  • 782 posts

Posted 21 October 2016 - 09:13 PM

View PostAraklaj, on 21 October 2016 - 09:56 AM, said:

That seems to have solved the issue! Interesting behavior.

Excellent! I'd double check that you have the latest versions of both the server and client; it's possible that you were hitting a bug that's already been fixed.

#11 Matt Janulewicz

Matt Janulewicz

    Advanced Member

  • Members
  • PipPipPip
  • 154 posts
  • LocationSan Francisco, CA

Posted 21 October 2016 - 09:28 PM

View PostSambwise, on 21 October 2016 - 09:13 PM, said:

Excellent! I'd double check that you have the latest versions of both the server and client; it's possible that you were hitting a bug that's already been fixed.

... or that your Perforce server is too old to know what '--parallel' is in the context of a submit ...
-Matt Janulewicz
Staff SCM Engineer, Perforce Administrator
Dolby Laboratories, Inc.
1275 Market St.
San Francisco, CA 94103, USA
majanu@dolby.com

#12 Sambwise

Sambwise

    Advanced Member

  • Members
  • PipPipPip
  • 782 posts

Posted 21 October 2016 - 11:58 PM

That'd get you a loud angry error message instead.  :)  P4V should generally be smart enough not to use a flag that the server straight up doesn't support; it checks the server version and will disable functionality as needed.

#13 Matt Janulewicz

Matt Janulewicz

    Advanced Member

  • Members
  • PipPipPip
  • 154 posts
  • LocationSan Francisco, CA

Posted 22 October 2016 - 12:32 AM

View PostSambwise, on 21 October 2016 - 11:58 PM, said:

That'd get you a loud angry error message instead.  :)  P4V should generally be smart enough not to use a flag that the server straight up doesn't support; it checks the server version and will disable functionality as needed.

Of course, you're right.

In any case, disabling feature to get a submit to work is more of a workaround than a solution. Still smells a bit like a bug to me and the OP should heed Steph's advice and open a ticket on it, methinks.
-Matt Janulewicz
Staff SCM Engineer, Perforce Administrator
Dolby Laboratories, Inc.
1275 Market St.
San Francisco, CA 94103, USA
majanu@dolby.com

#14 p4steph

p4steph

    Member

  • Members
  • PipPip
  • 19 posts

Posted 22 October 2016 - 12:45 AM

if you want to know more about this issue, feel free to reach out to me offline at steph@swervelogic.com

steph

    On Friday, October 21, 2016 5:35 PM, Matt Janulewicz <perforce-user-forum@forums.perforce.com> wrote:


Posted on behalf of forum user 'Matt Janulewicz'.



[http://forums.perfor...post&pid=20586]
Sambwise, on 2016/10/21 23:58:20 UTC, said:

Quote

    That'd get you a loud angry error message instead.� :) �P4V should generally be smart enough not to use a flag that the server straight up doesn't support; it checks the server version and will disable functionality as needed.
   
Of course, you're right.

In any case, disabling feature to get a submit to work is more of a workaround
than a solution. Still smells a bit like a bug to me and the OP should heed
Steph's advice and open a ticket on it, methinks.



--
Please click here to see the post in its original format:
  http://forums.perfor...changes-at-once

_______________________________________________
perforce-user mailing list  -  perforce-user@perforce.com
http://maillist.perf...o/perforce-user



_______________________________________________
perforce-user mailing list  -  perforce-user@perforce.com
http://maillist.perf...o/perforce-user







Also tagged with one or more of these keywords: Unreal engine

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users