Actions
Bug #8385
closedNative Scheduler does not properly track Core exit code
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