Bug #6542: Provide proper description about job or task fails in native scheduler - Klever - Open-Source Projects

Custom queries

Important bugs and features

Actions

Copy link

Bug #6542

closed

Provide proper description about job or task fails in native scheduler

Added by Ilja Zakharov over 8 years ago. Updated about 7 years ago.

Status:

Closed

Priority:

Urgent

Assignee:

Ilja Zakharov

Category:

Scheduling

Target version:

Start date:

01/28/2016

Due date:

% Done:

Estimated time:

Detected in build:

svn

Platform:

Published in build:

Description

Native scheduler does not provide detailed description to Bridge about reasons of task or job fails.

Related issues 3 (0 open — 3 closed)

Related to Klever - Feature #6540: Merge scheduler job and task clients code

Closed

Ilja Zakharov

01/28/2016

Actions

Related to Klever - Feature #8180: Schedulers should treat BenchExec warnings as errors

Closed

Ilja Zakharov

05/02/2017

Actions

Blocked by Klever - Bug #7408: Klever should properly report errors related with control groups

Rejected

07/18/2016

Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

Updated by Ilja Zakharov over 8 years ago

Category set to Scheduling

Actions

Copy link

Updated by Evgeny Novikov over 8 years ago

I am wondering whether schedulers of other types provide good description of job and task fails?

Actions

Copy link

Updated by Evgeny Novikov over 8 years ago

Priority changed from Low to High

Users definitely need clear understanding what issues happen.

Actions

Copy link

Updated by Evgeny Novikov almost 8 years ago

Assignee set to Ilja Zakharov
Priority changed from High to Immediate

Many users suffer from this, especially, when the production mode or/and removing working directories are used.

Actions

Copy link

Updated by Evgeny Novikov almost 8 years ago

Please, see one of important and often failures in #7408.

Actions

Copy link

Updated by Evgeny Novikov over 7 years ago

Priority changed from Immediate to Urgent

The immediate task that wasn't done during 4 months isn't immediate.

Actions

Copy link

Updated by Ilja Zakharov about 7 years ago

Status changed from New to Resolved

Implemented in scheduler-optimization.

Currently, I collect all exceptions and warnings and errors from RunExec and BenchExec. The only issue is that I send only the last message with the error. For instance, for job failings, it is enough just to show the reason and for most cases it really looks nice (including swap and cgroup support). But I noticed that for task solution the same messages are used for an RSB report and for this purpose additional information might be helpful. My proposal is to send all warnings and errors to Bridge but to make it showing for job failings only the last line.

Actions

Copy link

Updated by Evgeny Novikov about 7 years ago

Ilja Zakharov wrote:

Implemented in scheduler-optimization.

But I noticed that for task solution the same messages are used for an RSB report and for this purpose additional information might be helpful.

Can you provide any examples? I guess that anyway now the situation is much better then before when there were messages like "Task solution was finished with exit code ...". But it isn't clear what error messages are transmitted from schedulers.

Actions

Copy link