# Synthetic P4LOG fixture: database wedge scenario
# Signature: write lock on db.rev held by one process, pile-up of waiting processes
# TODO: Expand with realistic lock tracking records (requires server=3 track=1)
# Reference: go-libp4dlog p4dlog_test.go for field format details

Perforce server info:
	2024/01/15 14:30:00 pid 5001 admin@workstation [10.0.0.10] 'p4 submit -c 9999'

--- lapse 45.200s
--- db.rev
---   total lock wait+held read/write 0ms+0ms/0ms+45200ms

Perforce server info:
	2024/01/15 14:30:01 pid 5002 user1@client1 [10.0.0.1] 'p4 sync'

--- lapse 44.800s
--- db.rev
---   total lock wait+held read/write 44800ms+0ms/0ms+0ms

Perforce server info:
	2024/01/15 14:30:01 pid 5003 user2@client2 [10.0.0.2] 'p4 sync'

--- lapse 44.750s
--- db.rev
---   total lock wait+held read/write 44750ms+0ms/0ms+0ms

Perforce server info:
	2024/01/15 14:30:01 pid 5004 user3@client3 [10.0.0.3] 'p4 diff2'

--- lapse 44.700s
--- db.rev
---   total lock wait+held read/write 44700ms+0ms/0ms+0ms