This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: 'jules' locking libstdc++-v3 for > 15 minutes!
- From: Ian Lance Taylor <ian at airs dot com>
- To: Paolo Carlini <pcarlini at suse dot de>
- Cc: gcc at gcc dot gnu dot org, overseers at gcc dot gnu dot org
- Date: 20 May 2005 11:17:33 -0400
- Subject: Re: 'jules' locking libstdc++-v3 for > 15 minutes!
- References: <428DFCD1.8050704@suse.de>
Paolo Carlini <pcarlini@suse.de> writes:
> I have been waiting for > 15 minutes for 'jules' to unlock the library:
> how is this even possible? Are there operations taking *so* much time?
> Is there something I can do in such cases?
The process is now finished.
It was, I believe, a merge to csl-arm-branch. Presumably a lot of
files were being modified. Doing a commit on a branch is time
consuming. While the commit is happening, all the affected
directories are locked. The load on gcc.gnu.org was running in the 15
to 20 range at the time--this is not unusual, but of course means that
CVS operations are not as fast as possible.
There is nothing you can do when something like this is happening,
except wait.
People working on specifically targeted branches like csl-arm-branch
can make things better by merging one directory at a time, rather than
merging the whole tree at once. Of course you can only do this safely
if you can tell everybody using the branch to avoid using it until the
entire set of merges is complete. But when that is possible, it will
not lock up the repository so long for everybody else.
Ian