-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
execvp: catkin_generated/env_cached.sh: Text file busy #438
Comments
What is the output of |
I'm soo sorry for the late reply. My catkin config is nothing special (I guess); linked and using ccache (see below). I did not capture
|
Your description sounds very much like the installspace mutexing problem (#378, #391). I would have thought a linked develspace would be safe from that, but perhaps not. In any case, the fix in #391 only mutexes writes to the installspace, since that's my use case. So at the very least, you could try switching your config to that, eg:
If you want to play with reproducing these kinds of issues, feel free to rip off my little script for repeatedly building a small workspace in an attempt to trigger the problem, in #378 (comment). @jbohren is the architect of the linked develspace, so he'd know better how this is all supposed to be handled in there. |
System Info
Linux ABTZ0E9E 3.13.0-108-generic #155-Ubuntu SMP Wed Jan 11 16:58:52 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Python 2.7.6
Build / Run Issue
catkin build
, did not test withcatkin_make*
, see below.Expected Behavior
If I type
catkin build
, my packages should build.Actual Behavior
Most of the time, it actually works fine, but in some cases I get the following strange error when building a catkin package (called
PACKAGE
here). If I just do acatkin build
again, it typically works. It also happens for different packages with no clear structure.I typically get this output:
Steps to Reproduce the Issue
Unfortunately, it's hard to reproduce, because it happens sporadically. Repeat the following until you see the error:
:-(
The text was updated successfully, but these errors were encountered: