Specify greater wall time limits
At the moment wall time limits are almost the same as CPU time limits which isn't great at all.
Unfortunately this can't be implemented via benchmarks due to this issue.
Updated by Evgeny Novikov over 1 year ago
- Priority changed from High to Urgent
BTW, because of this issue I got wall timeouts for verification tasks requiring ~7.5 minutes of CPU time with timelimit equal to 15 minutes. This depends on a server load and hardware characteristics, but this is very bad from the benchmarking point of view. We need to find any solution. Perhaps we can disable wall timeouts in BenchExec and enforce them in scheduler workers ourselves.
Updated by Evgeny Novikov about 1 year ago
- Status changed from Resolved to Open
There is little sense to proceed to testing and for merging this branch to master as it needs again a way to install and to configure non-standard versions of BenchExec. I won't be surprised if everything will fail with current automatic deployments.
Updated by Evgeny Novikov 12 months ago
lost their relations with unknown reports at all, while there is one new associated mark 94cda75e1c23421736e612ef4131c545 (normal CPU timeout).
This changes are because BenchExec allows to detect CPU timeouts in the way we need.
To fix new issues, please, see at the attached job archive.