-
Notifications
You must be signed in to change notification settings - Fork 463
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
[VL] Pretty log native fallback reason #4494
Conversation
Thanks for opening a pull request! Could you open an issue for this pull request on Github Issues? https://github.com/oap-project/gluten/issues Then could you also rename commit message and pull request title in the following format?
See also: |
Run Gluten Clickhouse CI |
2 similar comments
Run Gluten Clickhouse CI |
Run Gluten Clickhouse CI |
153b353
to
1566bf7
Compare
Run Gluten Clickhouse CI |
could someone help review and rerun failed CI jobs? I have checked these failed CI jobs all due to network issue. cc @PHILO-HE @ulysses-you |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your work! Just two trivial comments.
@@ -29,6 +29,20 @@ | |||
namespace gluten { | |||
|
|||
namespace { | |||
#define LOG_VALIDATION_MSG_FROM_EXCEPTION(err) \ | |||
logValidateMsg(fmt::format( \ | |||
"Validation failed due to exception caught at file:{} line:{} function:{}, thrown from file:{} line:{} function:{} reason:{}", \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It may be better to contain exception position if debug is enabled? Ditto for LOG_VALIDATION_MSG.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I prefer keeping these information to help us quickly find root fallback reason, we may not ask customer re-run with debug mode enabled, customer's resources and patience not always enough.
Run Gluten Clickhouse CI |
@@ -42,7 +42,7 @@ object ValidationResult { | |||
ok | |||
} else { | |||
val fallbackInfo = info.getFallbackInfo.asScala | |||
.mkString("native check failure:", ", ", "") | |||
.mkString("Native validation failed:\n ", "\n ", "") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: remove blank after '\n'
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
these two blanks represent next line's indent.
(4) SortAggregate: Native validation failed:
Validation failed xxx
Validation failed xxx
(9) SortAggregate: Native validation failed:
Validation failed xxx
Validation failed xxx
(4) SortAggregate: Native validation failed:
Validation failed xxx
Validation failed xxx
(9) SortAggregate: Native validation failed:
Validation failed xxx
Validation failed xxx
Can we just leave a file name instead of full file path? We should make it brief, as well as informative. BTW, it may look better to clearly separate reason part from thrown from xxxx part, e.g. "thrown from xxx. Reason: xxx." |
Run Gluten Clickhouse CI |
ok. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thank you @Yohahaha
===== Performance report for TPCH SF2000 with Velox backend, for reference only ====
|
What changes were proposed in this pull request?
Introduce two new macros in native to enhance validation log:
LOG_VALIDATION_MSG_FROM_EXCEPTION
,LOG_VALIDATION_MSG
, then help developer check root cause easily.Before:
After: