Write error status when CC exited with code non-zero

[arukuka]

Summary

• write /Db/result/*/status_ERROR when CC exited with code non-zero

Purpose

• If CC was aborted, client could not know correct job status

Contents

• Change wrapper script
  • Use infinite loop
  • Write /Db/result/*/status_ERROR before launching CC if status_COMPLETED or status_ERROR were not written

Testing Methods Performed

• Run demo

  • Add code which occurs SIGSEGV in specific job

  • patch

    diff --git a/src/ComputationContainer/Job/Jobs/CorrelJob.hpp b/src/ComputationContainer/Job/Jobs/CorrelJob.hpp
    index 565b0e43..d486d4d3 100644
    --- a/src/ComputationContainer/Job/Jobs/CorrelJob.hpp
    +++ b/src/ComputationContainer/Job/Jobs/CorrelJob.hpp
    @@ -18,6 +18,8 @@ public:
             const std::vector<std::list<int>> &arg
         )
         {
    +        int *ptr = nullptr;
    +        *ptr = 1;
             std::list<std::vector<Share>> cols;
             for (const auto &w : arg[0])
             {

• Use ShellCheck for static analysis