public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
* stale cvs lock in src/gdb
@ 2012-02-16 13:11 Tristan Gingold
  2012-02-16 15:55 ` Ian Lance Taylor
  0 siblings, 1 reply; 3+ messages in thread
From: Tristan Gingold @ 2012-02-16 13:11 UTC (permalink / raw)
  To: overseers

Hi,

looks like there is a stale lock:

…
cvs commit: [12:39:10] waiting for anoncvs's lock in /cvs/src/src/gdb
cvs commit: [12:39:40] waiting for anoncvs's lock in /cvs/src/src/gdb
cvs commit: [12:40:10] waiting for anoncvs's lock in /cvs/src/src/gdb
cvs commit: [12:40:40] waiting for anoncvs's lock in /cvs/src/src/gdb
cvs commit: [12:41:10] waiting for anoncvs's lock in /cvs/src/src/gdb
cvs commit: [12:41:40] waiting for anoncvs's lock in /cvs/src/src/gdb
cvs commit: [12:42:10] waiting for anoncvs's lock in /cvs/src/src/gdb
cvs commit: [12:42:40] waiting for anoncvs's lock in /cvs/src/src/gdb
cvs commit: [12:43:10] waiting for anoncvs's lock in /cvs/src/src/gdb
cvs commit: [12:43:41] waiting for anoncvs's lock in /cvs/src/src/gdb
cvs commit: [12:44:11] waiting for anoncvs's lock in /cvs/src/src/gdb
cvs commit: [12:44:41] waiting for anoncvs's lock in /cvs/src/src/gdb
cvs commit: [12:45:12] waiting for anoncvs's lock in /cvs/src/src/gdb

Thanks,
Tristan.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: stale cvs lock in src/gdb
  2012-02-16 13:11 stale cvs lock in src/gdb Tristan Gingold
@ 2012-02-16 15:55 ` Ian Lance Taylor
  2012-02-17  8:07   ` Tristan Gingold
  0 siblings, 1 reply; 3+ messages in thread
From: Ian Lance Taylor @ 2012-02-16 15:55 UTC (permalink / raw)
  To: Tristan Gingold; +Cc: overseers

Tristan Gingold <gingold@adacore.com> writes:

> looks like there is a stale lock:
>
> …
> cvs commit: [12:39:10] waiting for anoncvs's lock in /cvs/src/src/gdb
> cvs commit: [12:39:40] waiting for anoncvs's lock in /cvs/src/src/gdb
> cvs commit: [12:40:10] waiting for anoncvs's lock in /cvs/src/src/gdb
> cvs commit: [12:40:40] waiting for anoncvs's lock in /cvs/src/src/gdb
> cvs commit: [12:41:10] waiting for anoncvs's lock in /cvs/src/src/gdb
> cvs commit: [12:41:40] waiting for anoncvs's lock in /cvs/src/src/gdb
> cvs commit: [12:42:10] waiting for anoncvs's lock in /cvs/src/src/gdb
> cvs commit: [12:42:40] waiting for anoncvs's lock in /cvs/src/src/gdb
> cvs commit: [12:43:10] waiting for anoncvs's lock in /cvs/src/src/gdb
> cvs commit: [12:43:41] waiting for anoncvs's lock in /cvs/src/src/gdb
> cvs commit: [12:44:11] waiting for anoncvs's lock in /cvs/src/src/gdb
> cvs commit: [12:44:41] waiting for anoncvs's lock in /cvs/src/src/gdb
> cvs commit: [12:45:12] waiting for anoncvs's lock in /cvs/src/src/gdb

Stale CVS locks are rare, because the locks include a PID, and if the
PID does not exist the lock is automatically broken.  I suspect this was
an anonymous CVS checkout over a slow network link.  In any case I don't
see any lock there now.  Let us know if you are still having trouble.

Ian

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: stale cvs lock in src/gdb
  2012-02-16 15:55 ` Ian Lance Taylor
@ 2012-02-17  8:07   ` Tristan Gingold
  0 siblings, 0 replies; 3+ messages in thread
From: Tristan Gingold @ 2012-02-17  8:07 UTC (permalink / raw)
  To: Ian Lance Taylor; +Cc: overseers


On Feb 16, 2012, at 4:54 PM, Ian Lance Taylor wrote:

> Tristan Gingold <gingold@adacore.com> writes:
> 
>> looks like there is a stale lock:
>> 
>> …
>> cvs commit: [12:39:10] waiting for anoncvs's lock in /cvs/src/src/gdb
>> cvs commit: [12:39:40] waiting for anoncvs's lock in /cvs/src/src/gdb
>> cvs commit: [12:40:10] waiting for anoncvs's lock in /cvs/src/src/gdb
>> cvs commit: [12:40:40] waiting for anoncvs's lock in /cvs/src/src/gdb
>> cvs commit: [12:41:10] waiting for anoncvs's lock in /cvs/src/src/gdb
>> cvs commit: [12:41:40] waiting for anoncvs's lock in /cvs/src/src/gdb
>> cvs commit: [12:42:10] waiting for anoncvs's lock in /cvs/src/src/gdb
>> cvs commit: [12:42:40] waiting for anoncvs's lock in /cvs/src/src/gdb
>> cvs commit: [12:43:10] waiting for anoncvs's lock in /cvs/src/src/gdb
>> cvs commit: [12:43:41] waiting for anoncvs's lock in /cvs/src/src/gdb
>> cvs commit: [12:44:11] waiting for anoncvs's lock in /cvs/src/src/gdb
>> cvs commit: [12:44:41] waiting for anoncvs's lock in /cvs/src/src/gdb
>> cvs commit: [12:45:12] waiting for anoncvs's lock in /cvs/src/src/gdb
> 
> Stale CVS locks are rare, because the locks include a PID, and if the
> PID does not exist the lock is automatically broken.  I suspect this was
> an anonymous CVS checkout over a slow network link.  In any case I don't
> see any lock there now.  Let us know if you are still having trouble.

Thanks.  It has been fixed.  Maybe it was a very very slow checkout as it was stale for several hours.

Tristan.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2012-02-17  8:07 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-02-16 13:11 stale cvs lock in src/gdb Tristan Gingold
2012-02-16 15:55 ` Ian Lance Taylor
2012-02-17  8:07   ` Tristan Gingold

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).