Project

General

Profile

Actions
Copy link

Bug #8385

closed

Native Scheduler does not properly track Core exit code

Added by Evgeny Novikov about 7 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Immediate
Assignee:
Ilja Zakharov
Category:
Scheduling
Target version:
0.1
Start date:
08/24/2017
Due date:
% Done:

0%

Estimated time:
Detected in build:
svn
Platform:
Published in build:

Description

For instance, Core exits with "1" but Native Scheduler says that its exit code is "0" (perhaps always).

This is one more crucial issue related with recent fixes and improvements in schedulers.

Actions
Copy link
 #1

Updated by Evgeny Novikov about 7 years ago

  • Target version set to 0.1
Actions
Copy link
 #2

Updated by Ilja Zakharov about 7 years ago

  • Status changed from New to Resolved

Fixed in core-exit-code-8385.

Actions
Copy link
 #3

Updated by Evgeny Novikov about 7 years ago

  • Status changed from Resolved to Closed

Works good! So, I merged the branch to master in b583aae7.

In addition this branch brings an interface incompatibility fix for VerifierCloud Scheduler.

Actions
Copy link

Also available in: Atom PDF