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
F13212471: D19174.diff
Fri, May 17, 6:45 AM
F13202045: D19174.id45928.diff
Tue, May 14, 8:54 PM
F13196065: D19174.diff
Sun, May 12, 10:54 PM
F13179782: D19174.diff
Wed, May 8, 9:26 PM
Unknown Object (File)
Sat, May 4, 7:06 PM
Unknown Object (File)
Wed, May 1, 12:01 AM
Unknown Object (File)
Sun, Apr 21, 9:27 PM
Unknown Object (File)
Mar 31 2024, 2:20 AM
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.