Correct. I don't think you are framing this correctly, as I don't recommend
you going into the rabbit hole of trying to recover from the segfault. Let
it crash and mark the full suite as failed.
The option is to execute each suite on separate invocations of nose /
python and then merge the xunit
Thank you Pedro. But this would still crash the nosetests process and thus
prevent the summary from being created, right?
On Thu, Jun 21, 2018 at 11:14 PM Pedro Larroy
wrote:
> A crash in the library is not an error in the test, is a different
> situation.
>
> I suggest adding these flags to
A crash in the library is not an error in the test, is a different
situation.
I suggest adding these flags to get stack traces and addressing the crash
as a separate bug.
https://github.com/larroy/mxnet/commit/46389e5851a60d06c37755e5772e6cbcd71b0080
Check the return code when executing the
Hello,
is anybody aware of a way to catch segmentation faults as part of the
nosetests execution and log them as ERROR? Right now, the nosetests process
gets terminated without a stack trace or further test execution. This has
additional significance because our result-recording that has been
