Skip to content

Conversation

@Lunderberg
Copy link
Contributor

Follow-up from #11235, all error messages should be based on expressions that are not IterMapExpr.

cc @vinx13

Follow-up from apache#11235, all error
messages should be based on expressions that are not IterMapExpr.
@github-actions github-actions bot requested a review from vinx13 May 23, 2022 17:41
@junrushao
Copy link
Member

Shall we have a regression test over this? Thanks a lot!

@junrushao
Copy link
Member

Maybe not. It's more related to error reporting

@junrushao junrushao merged commit 5655fa8 into apache:main May 23, 2022
@Lunderberg Lunderberg deleted the no_pretty_print_itermapexpr branch May 23, 2022 20:50
@Lunderberg
Copy link
Contributor Author

Unfortunately, it does cause issues beyond error reporting. By attempting to print an unsupported type, this bug called LOG(FATAL) instead of recording the context for later checks. Some paths do turn these into errors (e.g. through IndexMap), but others do not (e.g. through tvm::arith::EstimateRegionLowerBound which @vinx13 ran into earlier today).

Which is all to say that I've made a regression test, and am going to open a PR to add it.

Lunderberg added a commit to Lunderberg/tvm that referenced this pull request May 23, 2022
Follow-up from apache#11412, adding a
regression test for the bugfix.
junrushao pushed a commit that referenced this pull request May 24, 2022
Follow-up from #11412, adding a
regression test for the bugfix.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants