-
Notifications
You must be signed in to change notification settings - Fork 13
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
verrou_dd usability issues #7
Comments
Note that these ideas are based on my experience with verrou v1.1.0, but looking at the upcoming release notes, it looks like some of them are already in the process of being addressed. |
Thanks a lot for your insight. For future reference, here are a few thoughts/comments about the issues you mention.
|
Regarding point 5 ( When the Of course, if you have enough computational power, the optimal parallel setting is obtained when |
|
These remaining two issues start to stray a bit apart from the original ergonomics focus, so maybe it would be better to split them into two new tickets. Shall I do that? |
Yes, please create new issues for points 3. and 5. I believe 6525492 fixes the last ambiguous error message in |
Besides #6 , another issue which I have with verrou_dd is that it is a bit difficult to use correctly. Here are some suggestions of quality-of-life improvements:
verrou_dd
should accept relative paths to the run_script and cmp_scriptverrou_dd
should run the scripts from its initial working directory in order to remove the need for cumbersome absolute paths inside of said scripts => Probably not a good idea, as applications may leave state around in the working directory and we aim for independent runs.verrou_dd
could be better at detecting when the dd.sym cache must be invalidated. => Moved to Improving verrou_dd cache invalidation #9verrou_dd
's interface could be redesigned so that it is the one responsible for running verrou (or puts the proper valgrind command in an environment variable). This way, one would not need to repeat the valgrind command line in every run_script => Probably does not save enough characters to be useful, considering verrou_dd's requirementsverrou_dd
can take a lot of executions to converge, a way to state "my scripts are thread-safe, please fill up my idle CPU cores by testing multiple configurations in parallel" would be very nice. => In progress, parallel configuration testing is not there yet but parallel runs are in, see A proposal for a more efficient parallel verrou_dd #8The text was updated successfully, but these errors were encountered: