Jump to content


mister_wilson

Member Since 01 Mar 2013
Offline Last Active Apr 02 2019 03:05 PM
-----

Topics I've Started

P4V Undo changes does nothing for mixed depots

15 March 2019 - 09:34 PM

Hi,

I'm currently using P4V Rev. P4V/NTX64/2018.4/1753667 on Windows 10 and my server version is P4D/LINUX26X86_64/2016.2/1568552 (2017/09/20).

I wanted to revisit an issue that I reported last year https://forums.perfo.../page__hl__undo

I was able to determine that P4V's "Undo Changes..." operation does nothing on a submitted changelist that contains files from 2 different depots but running the operation on command line works fine
i.e.: p4 undo -c 562745 //...@562353

I was wondering if this issue was addressed or being looked at?

Thanks,

-Jonathan Wilson

P4V reconcile inconsistency

07 February 2019 - 04:46 PM

Hi,

I am currently using P4V version Rev. P4V/NTX64/2018.4/1753667 on Windows 10 and my server version is P4D/LINUX26X86_64/2016.2/1568552 (2017/09/20)

I seem to be experiencing a strange inconsistency with the p4 reconcile operation.
When I select the Reconcile Offline Work from P4V the operation works as expected (see attached screenshots 1, 2, and 3)

However when i try to run the same command from the command line (after selecting Open Command Window Here) nothing get reconciled.

i.e.:

p4 reconcile -c 1205131 -a -d -e -f //mydepot/SubmitAssistant/Default/...
//mydepot/SubmitAssistant/Default/... - no file(s) to reconcile.

Would anyone have any idea why the operation doesn't work via the command line?

Let me know if you need any additional information.

Thanks,

-Jonathan Wilson

Swarm - Unable to download zip file

14 January 2019 - 10:12 PM

Hi,

I am currently using Swarm Version 'SWARM/2018.1/1660025 (2018/05/09)' on Perforce server version P4D/LINUX26X86_64/2016.2/1568552 (2017/09/20).

On a particular swarm review I cannot seem to download the zip file attached to the review (see attachments).

The full error message is:
Error: Failed to archive '/opt/perforce/swarm-dunia/data/clients/6A77696C736F6E/swarm-459792cd-dddb-0dd4-6307-553c6466f255/turing/dev/main/Code/AgentGroupImpl/SupportServices/CloakSupportGroupDataModule.criteria.generated.cpp'. Exit status: 12. Output: zip error: Nothing to do! (try: zip -y -1 -r /opt/perforce/swarm-dunia/data/cache/archives/swarm-review-1461142.zip . -i CloakSupportGroupDataModule.criteria.generated.cpp)

The error message seems to be related to a file that was moved/renamed (attachment #3). Is there any way to resolve this issue?

Let me know if you need any additional information.

Thanks,

-Jonathan Wilson

Question about restricting submits from specific folders using wildcards

03 December 2018 - 07:42 PM

Hi,

I would like to restrict submits to 2 particular folders using p4 protect.

The folders are:

//mydepot/mybranch/data/generated/...
//mydepot/mybranch/data/Worlds/myworld/generated/...

In this example I would just do

=write group * * -//mydepot/mybranch/data/generated/...
=write group * * -//mydepot/mybranch/data/Worlds/myworld/generated/...

Now I would like to apply this restriction for any *branch* under mydepot and any *world* under Worlds, could someone tell me the best way to do it?
I was thinking of using the following syntax:

=write group * * -//mydepot/.../data/generated/...
=write group * * -//mydepot/.../data/Worlds/.../generated/...

or even to have it applicable to any depot

=write group * * -//.../data/generated/...
=write group * * -//.../data/Worlds/.../generated/...

Would this be the proper syntax?

Thanks,

-Jonathan Wilson

Strange submit error message

13 November 2018 - 09:36 PM

Hi,

I'm currently using P4V Rev. P4V/NTX64/2018.3/1719707 on a Windows 10 workstation and my server version is P4D/LINUX26X86_64/2016.2/1568552 (2017/09/20).

When I try to submit a changelist to perforce I get the following error message:


Submit aborted -- fix problems then use 'p4 submit -c 1100719'.
Revision //mydepot/tools-releases/mybranch/bin/AgentGroup_r64.dll#94 already exists! A submit operation attempted to overwrite this revision with a new file at the same revision. This should never happen, and therefore the server has aborted the submit. It is possible that the Perforce database files have been corrupted by a disk failure, system crash, or improper restore operation. Please contact Perforce technical support for assistance. Please do not perform any further operations on the server until the problem can be resolved. Please save all server logs, journals, and database tables for use in determining the necessary recovery operations.  

When I check the head revision of this file in perforce using fstat I can see that revision #93 is the latest submitted.

Would you happen to have any idea what the problem is here?

I'm not sure if this is related but last night I also noticed another error "The filesystem 'P4LOG' has only 844.1M free, but the server configuration requires at least 1G available"
Could this be related?

Let me know if you need any additional information.

Thanks,

-Jonathan Wilson