# The form data below was edited by tom_tyler # 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: HMS-1 Status: closed Project: perforce_software-hms Severity: C ReportedBy: albert ReportedDate: 2019/07/27 12:42:38 ModifiedBy: tom_tyler ModifiedDate: 2021/04/15 17:57:54 OwnedBy: tom_tyler Description: hms_ts_setup.sh isn't picking up "."/dot depots, e.g. "//.swarm" From the log: .... Loading depot spec file dot_swarm.depot.p4s. hms_ts_setup.sh: FATAL: Failed to load depot spec file dot_swarm.depot.p4s with contents: Depot: .swarm After commenting out lines to ignore the above issue, user hits this: .... Starting new HMS instance of p4d. Setting P4JOURNAL in the database to /p4/hms/logs/journal. /p4/hms/bin/p4d_hms -r /p4/hms/root -cset P4JOURNAL=/p4/hms/logs/journal Failed to rotate journal. Aborting p4d server start. hms_ts_setup.sh: FATAL: Failed to start new HMS instance. .... Component: setup Type: Bug