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
F19505767: D19174.diff
Fri, Jan 9, 2:04 PM
F19505765: D19174.diff
Fri, Jan 9, 2:03 PM
F19505407: D19174.diff
Fri, Jan 9, 11:28 AM
F19153130: D19174.id45928.diff
Dec 11 2025, 7:43 AM
F19072675: D19174.diff
Nov 30 2025, 11:11 PM
F19069839: D19174.diff
Nov 30 2025, 3:06 PM
F19069700: D19174.diff
Nov 30 2025, 3:00 PM
F19069691: D19174.diff
Nov 30 2025, 3:00 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.