Page MenuHomePhabricator

Add a "lock log" for debugging where locks are being held
ClosedPublic

Authored by epriestley on Mar 5 2018, 11:27 PM.
Tags
None
Referenced Files
F14336317: D19174.id45928.diff
Wed, Dec 18, 5:49 PM
F14329445: D19174.diff
Wed, Dec 18, 3:16 PM
Unknown Object (File)
Fri, Dec 13, 5:17 AM
Unknown Object (File)
Tue, Dec 10, 10:58 PM
Unknown Object (File)
Tue, Dec 10, 11:59 AM
Unknown Object (File)
Sat, Nov 30, 8:08 AM
Unknown Object (File)
Thu, Nov 28, 12:28 AM
Unknown Object (File)
Tue, Nov 19, 8:07 PM
Subscribers
None

Details

Summary

Depends on D19173. Ref T13096. Adds an optional, disabled-by-default lock log to make it easier to figure out what is acquiring and holding locks.

Test Plan

Ran bin/lock log --enable, --disable, --name, etc. Saw sensible-looking output with log enabled and daemons restarted. Saw no additional output with log disabled and daemons restarted.

Diff Detail

Repository
rP Phabricator
Branch
lock2
Lint
Lint Warnings
SeverityLocationCodeMessage
Warningsrc/infrastructure/util/PhabricatorGlobalLock.php:155XHP79Global Variables
Unit
Tests Passed
Build Status
Buildable 19739
Build 26736: Run Core Tests
Build 26735: arc lint + arc unit

Event Timeline

This revision was not accepted when it landed; it landed in state Draft.Mar 6 2018, 1:55 AM
This revision was automatically updated to reflect the committed changes.