# 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: SDP-38 Status: open Project: perforce-software-sdp Severity: B ReportedBy: tom_tyler ReportedDate: 2017/04/02 17:24:28 ModifiedBy: tom_tyler ModifiedDate: 2020/03/28 17:55:44 OwnedBy: tom_tyler Description: checkpoint.log contains cruft from earlier failed run. On Linux, in cases where a checkpoint operation fails for some reason, the checkpoint.log file can contain cruft from the earlier failed run at the top, even though the current run is OK. Here's a sample log snippit: gzip: log.878.gz already exists; not overwritten gzip: p4broker.log.878.gz already exists; not overwritten gzip: audit.log.878.gz already exists; not overwritten Fri Feb 26 05:55:52 CST 2016 : Start p4_1 Checkpoint Fri Feb 26 05:55:52 CST 2016 : Create a new checkpoint from the live db files. Checkpointing to /p4/1/checkpoints/p4_1.ckp.879.gz... In this sample snippet, the first 3 lines prefixed with 'gzip: ' are error messages from the failed previous run, while the line starting with 'Fri Feb 26' is the "happy" output from the current run. Of course, the contents of checkpoint.log should be guaranteed discrete, and contain contents only from a single run. Fixing this must not change the property that the log file with with the static name 'checkpoint.log' must contain status from the most recent run, and logs with a known journal counter have that journal counter in the name. A new naming convention may be needed for rotated logs that don't have a clear journal number to associate. This snippet is from a customer site with a 2014-era SDP; not very old but about a year and a half behind current (as of Feb 2016). Component: core-unix Type: Bug