-
Notifications
You must be signed in to change notification settings - Fork 346
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
UI Improvements for Really Long Builds. #1991
Comments
A nicer lock management for these cases would be nice too. |
This is feasible, we are using a sigalarm, so it would be possible to do the same in non-verbose mode, but with a longer delay (eg 5min) the first time, when the command starts. |
well, |
Releasing the switch lock completely would be quite dangerous: what if other packages were added / removed in the meantime ? Weakening it to a read lock during build could work, but I am not sure that would allow to do much more. What is it you're missing during these 20 minutes ? Another way would be to add an option to disable the lock with a "You're on your own" disclaimer... but I'd rather avoid this kind of non-features. |
Just a read lock would be useful for
|
These shoud work already: |
I was actually thinking of something like that, yes. But you're the one to know what is hard to implement, I'm just wishing. ;) Is it possible for opam to wait for the lock to be released and then proceed as usual, instead of failing ? |
I wouldn't do it by default, but adding an env variable for infinite wait would be very easy (a command-line option being slightly more work). Something like |
Lock handling is much finer now, and you shouldn't get stuck. Also, waiting until the lock is released is the default behaviour in interactive mode (and there is no wait, but a failure, in scripts). There is still no auto-verbose-toggle-after-5-mins, though |
I agree that the problem is mostly gone, but I'm not compiling a 20-minute project on a daily basis anymore. :) |
If the problem is solved, can the issue be closed? |
The lock issues are mostly gone, but @AltGr might still want to improve the UI. |
It would be nice to have a way to, interactively during builds, show the log, or to start showing the logs when a command has been going for a really long time.
I'm not thinking core-long, more like z3, full-llvm, coq.
The text was updated successfully, but these errors were encountered: