-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] [Unity] Fail to print out call trace under relax::Normalizer #15880
Comments
cc @Lunderberg |
seems is related to #15596 |
Thank you, and I'll take a look at it later this week. When catching in python, it resolved some out-of-order issues, but I hadn't checked if it also caused others. |
Ah, looks like the string isn't collecting the full stack track, only the python object. This becomes a problem if the error is caught in a context where the string is printed. |
Hi @Lunderberg just want to check if there's any progress on this issue |
Unfortunately, I haven't been able to reproduce the error so far on my side using your example. This was attempted in builds with and without debug symbols, with and without optimization enabled. While commenting out the What compiler are you using? I'm currently running on g++ 11.3.0, and maybe that causes a difference. |
Prior to this commit, the FFI error propagation in Python assumed that any stack frame with a known file name also had a known line number. This commit updates the error propagation to instead check if a known line number is present. Closes apache#15880.
That said, the |
Expected behavior
printing out call trace when encountering
ICHECK
failureActual behavior
Environment
TVM Unity TOT
Steps to reproduce
Comment out this line:
https://github.com/apache/tvm/blob/unity/src/relax/op/tensor/linear_algebra.cc#L150
and run tests/python/relax/test_op_linear_algebra.py
if you print out
frame
here, you will seecc @quic-sanirudh
The text was updated successfully, but these errors were encountered: