P4Convert sometimes throws warnings about case issues, then fails with the
following errors:
CASE-SENSITIVITY ISSUE:
From node is missing from dataset; skipping!
Please check case options and platform types.
com.p4convert.p4.caseMode = NONE
com.p4convert.p4.lowerCase = false
Caught exception on exit
java.nio.file.FileAlreadyExistsException: /logs/tmp/<Directory>
perforce_migration/<Dir>/p4_root/ws/svn/<Dir>/trunk/<Dir>/<Dir>/alpha/<Dir>/
<File>.cfg
at java.base/sun.nio.fs.UnixCopyFile.copy(Unknown Source)
at java.base/sun.nio.fs.UnixFileSystemProvider.copy(Unknown Source)
at java.base/java.nio.file.Files.copy(Unknown Source)
at com.perforce.svn.change.RevisionImport.duplicatePath(RevisionImport.java:172)
at com.perforce.svn.change.RevisionImport.branchPath(RevisionImport.java:128)
at com.perforce.svn.change.ChangeImport.addPath(ChangeImport.java:265)
at com.perforce.common.node.NodeImport.dirAction(NodeImport.java:63)
at com.perforce.common.node.NodeImport.action(NodeImport.java:49)
at com.perforce.svn.process.SvnProcessNode.processDir(SvnProcessNode.java:465)
at com.perforce.common.process.ProcessNode.process(ProcessNode.java:56)
at com.perforce.svn.process.SvnProcessChange.processChange(SvnProcessChange.java:
170)
at com.perforce.common.process.ProcessChange.call(ProcessChange.java:59)
at com.perforce.common.process.ProcessChange.call(ProcessChange.java:21)
at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)
Caught EXIT shutting down ...
The customer suspects a race condition. They say:
The case handling warning seems to be just that; a warning. The actual conversion
error is thrown regardless of if the warning is present or not. If you look at the
full log file I attached, the warning isn't present, but the same warning and
stack trace is. I believe there's a race condition present in the converter. If re-run the conversion a couple times, it gets past this error.
Unfortunately we can not obtain their data to try to reproduce the issue.
I am logging this job to record the problem.