Connection error warnings can lead to task decision results misinterpretation
Task decision results are also based on STDERR content and if it contains warnings due to several attempts of results uploading, then the scheduler thinks that the task is failed. This is implemented because BenchExec does not terminate the task in case of an incorrect setup of swap and cgroups and it can be ruled out only on base of STDERR.
We need to suppress these connection related warning since there are unimportant and can be printed in the rest log.
#1 Updated by Evgeny Novikov about 1 year ago
- teach BenchExec to provide warnings/errors better or to terminate programs in case of these warnings/errors,
- or/and to separately consider STDERR from BenchExec and from our scripts themselves since many unexpected messages could be printed by them there.