Actions
Bug #8668
closedConnection error warnings can lead to task decision results misinterpretation
Start date:
01/15/2018
Due date:
% Done:
0%
Estimated time:
Detected in build:
svn
Platform:
Published in build:
Description
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.
Updated by Evgeny Novikov over 6 years ago
I think that it really has sense to:
- 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.
Updated by Evgeny Novikov almost 6 years ago
- Related to Bug #8905: Take into account that Django development server is not powerful added
Updated by Evgeny Novikov almost 6 years ago
- Assignee set to Ilja Zakharov
- Priority changed from High to Urgent
- Target version set to 1.0
This issue was fixed together with #8905 in branch core-new-formats.
Updated by Evgeny Novikov almost 6 years ago
- Status changed from New to Resolved
Actions