Usability degradation #16102
Comments
Hey, this is the MXNet Label Bot. |
I think we should also test for the exceptions. We need to test import mxnet.numpy as np
from mxnet.base import MXNetError
try:
a = np.ones((10, 10))
b = a.reshape((1,))
except MXNetError:
pass
except:
raise |
I suspect this may be related to some variations on the nightly build platforms. I built the latest master from source on mac os; the error message and stack trace can be printed correctly. However, the latest nightly build gives the seg fault and the stack trace is irrelevant with the code. |
There are already tests for exception handling: https://github.com/apache/incubator-mxnet/blob/master/tests/python/unittest/test_exc_handling.py . The problem is we don't test for macos, do we ? Having said that this was working at some point in time, so as @reminisce suggests this may be issue only with specific builds. |
@anirudh2290 Have we tested the case for reshaping to an invalid shape? |
Agree, I think the issue is how we compile. Seems like we're stripping debug symbols. |
@sxjscience probably not. is this happening only with reshape ? |
I guess we failed to catch this usability degradation because we haven't tested the error message raised by reshape. I suggest adding this to the |
@zachgk assign [@sxjscience] |
@eric-haibin-lin I've added the check for exception handling. |
@anirudh2290 In terms of the mac OS CI, do you have any idea about that? @zhanghang1989 has observed some other problems in MXNet in macOS. I guess the ultimate solution is to enable the macOS CI. |
@sxjscience I have never built and run MXNet on macOS ! Its a good thought to add Macos to CI, though I think its a project in itself since there may be other failures. Till now, I don't know anyone working on it. |
@anirudh2290 Thanks... I'm considering to try it on my personal mac first to understand how many tests will fail... |
But recent build hides error messages:
The text was updated successfully, but these errors were encountered: