-
Notifications
You must be signed in to change notification settings - Fork 3
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
Problem with benchmark xml definition #8
Comments
Seems, the problem is due to launch not from tool directory, but why not to |
Option "benchmark file" specifies file, which should be executed by benchexec. Thus if you do not launch benchmark (option -l), that option is ignored. Currently there is no option for xml results file |
That is what exactly what I mean. I tried to launch the benchmark_visualizer on our verifier cloud from the deploy directory (with option -l). And it cannot found the benchmark.xml file until manually goes to the tool directory. I found all symlinks there, so, It has been already prepared the directory. The question is why does it not change the directory by itself? |
Benchmark processing script searches 'benchmark.xml' only in a current directory even if I set it up in configuration as "benchmark file". So, for now I have to make a link to it. Seems, the option is just ignored.
The text was updated successfully, but these errors were encountered: