Project

General

Profile

Bug #8668

Connection error warnings can lead to task decision results misinterpretation

Added by Ilja Zakharov about 1 year ago. Updated 9 months ago.

Status:
Closed
Priority:
Urgent
Assignee:
Category:
Scheduling
Target version:
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.


Related issues

Related to Klever - Bug #8905: Take into account that Django development server is not powerfulClosed2018-05-30

History

#1 Updated by Evgeny Novikov about 1 year ago

I think that it really has sense to:
  1. teach BenchExec to provide warnings/errors better or to terminate programs in case of these warnings/errors,
  2. or/and to separately consider STDERR from BenchExec and from our scripts themselves since many unexpected messages could be printed by them there.

#2 Updated by Evgeny Novikov 9 months ago

  • Related to Bug #8905: Take into account that Django development server is not powerful added

#3 Updated by Evgeny Novikov 9 months ago

  • Target version set to 1.0
  • Priority changed from High to Urgent
  • Assignee set to Ilja Zakharov

This issue was fixed together with #8905 in branch core-new-formats.

#4 Updated by Evgeny Novikov 9 months ago

  • Status changed from New to Resolved

#5 Updated by Evgeny Novikov 9 months ago

  • Status changed from Resolved to Closed

See #8905.

Also available in: Atom PDF