# The form data below was edited by jen_bottom # Perforce Workshop Jobs # # Job: The job name. 'new' generates a sequenced job number. # # Status: Job status; required field. There is no enforced or # promoted workflow for transition of jobs from one # status to another, just a set of job status values # for users to apply as they see fit. Possible values: # # open - Issue is available to be worked on. # # inprogress - Active development is in progress. # # blocked - Issue cannot be implemented for some reason. # # fixed - Fixed, optional status to use before closed. # # closed - Issue has been dealt with definitively. # # punted - Decision made not to address the issue, # possibly not ever. # # suspended - Decision made not to address the issue # in the immediate future, but noting that it may # have some merit and may be revisited later. # # duplicate - Duplicate of another issue that. # # obsolete - The need behind the request has become # overcome by events. # # Project: The project this job is for. Required. # # Severity: [A/B/C] (A is highest) Required. # # ReportedBy The user who created the job. Can be changed. # # ReportedDate: The date the job was created. Automatic. # # ModifiedBy: The user who last modified this job. Automatic. # # ModifiedDate: The date this job was last modified. Automatic. # # OwnedBy: The owner, responsible for doing the job. Optional. # # Description: Description of the job. Required. # # DevNotes: Developer's comments. Optional. Can be used to # explain a status, e.g. for blocked, punted, # obsolete or duplicate jobs. May also provide # additional information such as the earliest release # in which a bug is known to exist. # # Component: Projects may use this optional field to indicate # which component of the project a givenjob is associated # with. # # For the SDP, the list of components is defined in: # //guest/perforce_software/sdp/tools/components.txt # # Type: Type of job [Bug/Feature]. Required. # # Release: Release in which job is intended to be fixed. Job: job000749 Status: open Project: perforce-software-p4convert Severity: C ReportedBy: jen_bottom ReportedDate: 2020/03/06 09:39:24 ModifiedBy: jen_bottom ModifiedDate: 2020/03/06 09:39:24 Description: 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/ perforce_migration//p4_root/ws/svn//trunk///alpha// .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. Type: Bug