Message6707

Author silvan
Recipients jendrik, malte, silvan
Date 2017-12-05.09:37:26
Content
Thanks for all the input so far!

I finally ran some experiments. The first one only runs search configurations
and is intended to compare the before-after behavior of exit codes. I manually
translated the legacy to the new exit codes. The comparison looks fine:
http://ai.cs.unibas.ch/_tmp_files/sieverss/issue739-v2-search-issue739-base-issue739-v2-compare.html

For translator configurations that restrict time, everything is fine, too, but
for catching MemoryErrors, things are different. We successfully catch
MemoryError (in one task, the small memory limit led to a segfault) and return
the correct exit code, but python sometimes prints to stderr even though the
MemoryError is caught. When testing this locally, I cannot consistently
reproduce the behavior: sometimes, for the same task, there is output to stderr,
sometimes there isn't. The output also varies, I've seen lines like
"MemoryError" or "Exception MemoryError: MemoryError() in <object repr() failed>
ignored", and also cases where several such lines occurred (presumably due to
running out of memory again while printing, even though we reserve 10MB of
emergency memory).

http://ai.cs.unibas.ch/_tmp_files/sieverss/issue739-v2-translate.html

Any suggestions how to address this?
History
Date User Action Args
2017-12-05 09:37:26silvansetmessageid: <1512463046.14.0.156906544668.issue739@unibas.ch>
2017-12-05 09:37:26silvansetrecipients: + silvan, malte, jendrik
2017-12-05 09:37:26silvanlinkissue739 messages
2017-12-05 09:37:26silvancreate