Author silvan
Recipients jendrik, malte, silvan
Date 2017-10-16.14:03:57
Now that issue738 is integrated (which fixes translator crashs due to hitting
the memory limit), we could in principle distinguish between running out of
memory with the translator or the search. For other "results", such as hitting
the time limit (SIGXCPU, -24) or exiting with "0", we cannot make this
distinction (e.g. with lab). We would like to modify the driver to return
different exit codes for the translator and the search even if the exit code
returned by the components would be the same. This can help preventing problems
with the translator in future, such as the one we had when switching to slurm
where tasks could not be translated, instead of just assuming that "out of
memory" or "out of time" always means "search ran out time/memory".
Date User Action Args
2017-10-16 14:03:58silvansetrecipients: + silvan, malte, jendrik
2017-10-16 14:03:57silvansetmessageid: <>
2017-10-16 14:03:57silvanlinkissue739 messages
2017-10-16 14:03:57silvancreate