-
Notifications
You must be signed in to change notification settings - Fork 389
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
Running "dune coq top --no-build ..." tries to take the lock #7671
Comments
@rlepigre I'll look into it. We might be running coqdep causing the build to lock. I'll also write a cram so that we can preserve this behaviour. |
@Alizter did you ever try looking into this, or did you just not get the time? |
@rlepigre I remember investigating but I didn't find anything conclusive. The nobuuild was set up correctly as far as I could tell, but something was causing the global lock to trigger. |
OK cool. Now that I think about it, is it possible that this got fixed by #10446? |
@rlepigre I think it's unlikely, but I haven't checked. I think this issue was around before that bug was introduced. |
Expected Behavior
Running
dune coq top --no-build ...
should not fail if there is a concurrently runningdune build
command.Actual Behavior
You get:
Error: A running dune instance has locked the build directory
.Is there anything we can do to fix this? Or does
dune coq top --no-build ...
possibly need to build stuff?The text was updated successfully, but these errors were encountered: