Closed tfoote closed 10 years ago
There's a very recent ticket on this here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666525 It looks to be a race condition between the internal build user and the root chroot setup both using ccache.
There doesn't seem to be an easy work around (besides disabling ccache) while waiting for the patch. As it's a low percentage of our builds I"m going to close with a won't fix. We can reopen if the prevalence increases in the future.
Can you describe which concurrent uses are actually colliding? What does "internal build user" and "root chroot setup" stand for?
Would it be possible to separate both by giving one of them a custom CCACHE_BASEDIR
?
My summary is from the ticket. Find more details there. These are the users inside the pbuilder process, there's root and pbuilder users inside the chroot as you don't want to build as root.
That is the basic fix. They turn off CCACHE for the root invocations.
The fix is submitted upstream at http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=73;filename=pbuilder_ccache_666525.diff;att=1;bug=666525
We ran a full hydro cycle and got approximately 9 instances of this error.
It can happen both in the body of the build and early in the cmake test compiles.
A trigger missing red got things going again.