benchexec
benchexec copied to clipboard
BenchExec: A Framework for Reliable Benchmarking and Resource Measurement
Currently, the following happens at the end of a run in container mode: - Main process of tool is stopped (because it terminates or because it is killed due to...
In #402, it is suggested to parse the file loaded for link overlays if it is a task-definition file, and provide a richer and interactive view of the file for...
`runexec` has an option `--maxOutputSize` and will truncate the tool log if it exceeds the given size. However, this is applied only after the run ended. While the run is...
When a tool truncates the file descriptors that it has for `stdout` and `stderr`, this leads to truncation of the log file with the output. So a tool can undo...
Provide an option in the table definition and the user can set the column width to meaningful values. Some users anyway set the number of digits there in order to...
There are two sets of result files that BenchExec produces: - Log files (those results that the tool outputs to stdout) - Data files (those results that the tool outputs...
This benchmark definition: https://github.com/sosy-lab/sv-comp/blob/svcomp19/benchmark-defs/cpa-seq-validate-violation-witnesses.xml claims to follow the benchmark-definition format 1.4, but uses the tag `` which came only with version 1.9. Shouldn't BenchExec check the XML files that it...
For example benchexec -Dfoo=bar benchmark.xml would replace `${foo}` by `bar` in benchmark.xml just like `${rundefinition_name}`.
Sometimes the benchmarked process wants to use cgroups itself. BenchExec prevents this (in container mode) by mounting the cgroup hierarchy read-only. If we would not do this, the benchmarked process...
I noticed that, especially in runexecutor.RunExecutor, sys.exit() is used to handle error cases quite often. It's fine to simply exit the interpreter from code which is only meant to be...