{"action":"created","issue":{"url":"https://api.github.com/repos/sosy-lab/benchexec/issues/100","repository_url":"https://api.github.com/repos/sosy-lab/benchexec","labels_url":"https://api.github.com/repos/sosy-lab/benchexec/issues/100/labels{/name}","comments_url":"https://api.github.com/repos/sosy-lab/benchexec/issues/100/comments","events_url":"https://api.github.com/repos/sosy-lab/benchexec/issues/100/events","html_url":"https://github.com/sosy-lab/benchexec/issues/100","id":122234464,"number":100,"title":"Users need the way to specify their own wall time limits in benchmarks","user":{"login":"eunovm","id":16303309,"avatar_url":"https://avatars.githubusercontent.com/u/16303309?v=3","gravatar_id":"","url":"https://api.github.com/users/eunovm","html_url":"https://github.com/eunovm","followers_url":"https://api.github.com/users/eunovm/followers","following_url":"https://api.github.com/users/eunovm/following{/other_user}","gists_url":"https://api.github.com/users/eunovm/gists{/gist_id}","starred_url":"https://api.github.com/users/eunovm/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/eunovm/subscriptions","organizations_url":"https://api.github.com/users/eunovm/orgs","repos_url":"https://api.github.com/users/eunovm/repos","events_url":"https://api.github.com/users/eunovm/events{/privacy}","received_events_url":"https://api.github.com/users/eunovm/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/sosy-lab/benchexec/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-12-15T09:57:33Z","updated_at":"2016-04-09T13:24:18Z","closed_at":null,"body":"At the moment all benchmarks implicitly have the default wall time limit that is 30 seconds greater than a specified CPU time limit. Likely users need/want develop new benchmarks with explicit wall time limits. For old-style benchmarks new versions of BenchExec can issue warnings if wall time limits aren't specified.\r\nBTW, runexec already has an option to specify wall time limits explicitly, so its direct users can use it already."},"comment":{"url":"https://api.github.com/repos/sosy-lab/benchexec/issues/comments/207788794","html_url":"https://github.com/sosy-lab/benchexec/issues/100#issuecomment-207788794","issue_url":"https://api.github.com/repos/sosy-lab/benchexec/issues/100","id":207788794,"user":{"login":"cheshire","id":348959,"avatar_url":"https://avatars.githubusercontent.com/u/348959?v=3","gravatar_id":"","url":"https://api.github.com/users/cheshire","html_url":"https://github.com/cheshire","followers_url":"https://api.github.com/users/cheshire/followers","following_url":"https://api.github.com/users/cheshire/following{/other_user}","gists_url":"https://api.github.com/users/cheshire/gists{/gist_id}","starred_url":"https://api.github.com/users/cheshire/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cheshire/subscriptions","organizations_url":"https://api.github.com/users/cheshire/orgs","repos_url":"https://api.github.com/users/cheshire/repos","events_url":"https://api.github.com/users/cheshire/events{/privacy}","received_events_url":"https://api.github.com/users/cheshire/received_events","type":"User","site_admin":false},"created_at":"2016-04-09T13:24:18Z","updated_at":"2016-04-09T13:24:18Z","body":"I would really like to have a walltime-limit feature (as opposed to CPU time).\r\nFrom informal conversations with SV-COMP participants I gather that a _lot_ of people would prefer to measure timeouts by walltime rather than CPU time. Adding this feature to Benchexec would be a first step in evaluating how much difference that would make.\r\n\r\nThis is anecdotal and not really supported, but I have talked to about eight people who would prefer wall time limit instead of CPU time limit, and I haven't seen a single person arguing in favor of CPU time limit."}}