locking: clean up debug messages
We no longer need these for the issue we were debugging, and these
are pretty chatty in our builders where we run with --debug.
BUG=chromium:1095661
TEST=CQ passes
Change-Id: I4fde980ab7b726366c73df28f643f0ef30521e0e
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/chromite/+/2657810
Commit-Queue: Mike Frysinger <vapier@chromium.org>
Commit-Queue: Michael Mortensen <mmortensen@google.com>
Tested-by: Mike Frysinger <vapier@chromium.org>
Auto-Submit: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Michael Mortensen <mmortensen@google.com>
diff --git a/lib/locking.py b/lib/locking.py
index 167e814..f56751a 100644
--- a/lib/locking.py
+++ b/lib/locking.py
@@ -127,13 +127,10 @@
raise
except EnvironmentError as e:
if e.errno != errno.EDEADLK:
- message = ('%s: blocking wait failed errno %s'
- % (self.description, e))
+ logging.error('%s: blocking wait failed errno %s', self.description, e)
raise
self.unlock()
self.locking_mechanism(self.fd, flags)
- logging.debug('%s: lock has been acquired (%s), continuing.',
- self.description, self.locktype)
def lock(self, shared=False):
"""Take a lock of type |shared|.
@@ -199,8 +196,6 @@
IOError if the operation fails in some way.
"""
if self._fd is not None:
- logging.debug('%s: lock is being released (%s).',
- self.description, self.locktype)
self.locking_mechanism(self._fd, fcntl.LOCK_UN)
def __del__(self):