# The form data below was edited by scott_common
# 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: PSLA-5
Status: open
Project: perforce-software-log-analyzer
Severity: B
ReportedBy: scott_common
ReportedDate: 2020/10/15 07:53:52
ModifiedBy: scott_common
ModifiedDate: 2020/10/15 07:53:52
OwnedBy: scott_common
Description:
Storage lock data in 2019.1 and later logs skewing results.
The storageup, and I suppose the storageupmaster possibly, are putting lock times on
other tables.
$ log2sql --version
log2sql, version v0.8.1 (branch: master, revision: c834aaf)
build user: [email protected]
build date: 2020-09-05T19:01:35+0100
go version: go1.13.4
....
--- db.workingx
--- total lock wait+held read/write 0ms+31ms/0ms+1856ms
--- max lock wait+held read/write 0ms+31ms/0ms+1855ms
--- db.change
--- total lock wait+held read/write 7ms+1ms/2337ms+0ms
--- max lock wait+held read/write 7ms+1ms/2337ms+0ms
--- storageup/storageup(R)
--- total lock wait+held read/write 0ms+1635446ms/0ms+0ms
startTime endTime running user cmd pid tableName maxReadHeld maxWriteHeld totalReadWait totalReadHeld totalWriteWait
0 2020/10/13 16:55:29 2020/10/13 17:22:45 184 supadhyayula user-shelve 44149 change 1 0 0 1635446 0
DevNotes:
Type: Bug