[PATCH 4 of 4 STABLE] lock: show about possibility of lock corruption for empty locker

Matt Harbison mharbison72 at gmail.com
Sat Apr 29 11:28:14 EDT 2017


On Sat, 29 Apr 2017 04:38:10 -0400, FUJIWARA Katsunori  
<foozy at lares.dti.ne.jp> wrote:

> # HG changeset patch
> # User FUJIWARA Katsunori <foozy at lares.dti.ne.jp>
> # Date 1493454424 -32400
> #      Sat Apr 29 17:27:04 2017 +0900
> # Branch stable
> # Node ID 650d9f6bf1e7c1f6dee9d82616af2a56aaf56a2e
> # Parent  b64713f57a22301b6f481cd8e401542f46356c94
> lock: show about possibility of lock corruption for empty locker

> +  $ echo foo > foo
> +  $ hg add foo
> +  waiting for lock on working directory of $TESTTMP/t2, but might be  
> corrupted (glob)

Maybe "..., but the lock might be corrupted"?

It seems better to be very explicit when mentioning "working directory"  
and "corrupted" in the same sentence.

> +  abort: working directory of $TESTTMP/t2: timed out waiting for lock,  
> but might be corrupted (glob)

> +  (use 'hg debuglocks' to check/unlock corrupted lock)
> +  [255]
> +
> +(check still corrupted)
> +
> +  $ hg debuglocks
> +  lock:  free
> +  wlock: user *, but corrupted (*s) (glob)
> +  [1]
> +
> +(check normal waiting/timedout messages for safety, too)
> +
> +  $ printf '1234' > .hg/wlock
> +
> +  $ hg add foo
> +  waiting for lock on working directory of $TESTTMP/t2 held by '1234'  
> (glob)
> +  abort: working directory of $TESTTMP/t2: timed out waiting for lock  
> held by 1234 (glob)
> +  [255]
> +
> +  $ printf 'foobar:1234' > .hg/wlock
> +
> +  $ hg add foo
> +  waiting for lock on working directory of $TESTTMP/t2 held by process  
> '1234' on host 'foobar' (glob)
> +  abort: working directory of $TESTTMP/t2: timed out waiting for lock  
> held by foobar:1234 (glob)
> +  [255]
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at mercurial-scm.org
> https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


More information about the Mercurial-devel mailing list