[SPARK-37733][BUILD] Change log level of tests to WARN #35011
Conversation
github-actions
bot
added
AVRO
CORE
DSTREAM
GRAPHX
KUBERNETES
MESOS
SPARK SHELL
SQL
STRUCTURED STREAMING
YARN
labels
|
Kubernetes integration test starting |
|
Merged to master. |
|
Kubernetes integration test status failure |
|
Test build #146557 has finished for PR 35011 at commit
|
|
Hmm, changing log level seems causing some test failures, e.g. |
|
Shall we revert this first? Actually I merged #34965 which fixes logging issue for hive-thriftserver module that produces large log output a few hours ago. I think it already fixes the issue of this PR. The link @gengliangwang attached in the description is happened before. |
### What changes were proposed in this pull request? This reverts commit c0cedb1. ### Why are the changes needed? #35011 changes log level and causes some tests that check log message failed. Actually #34965 was merged not long ago which fixes logging issue for hive-thriftserver module that produces large log output. ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? Pass tests. Closes #35014 from viirya/revert-SPARK-37733. Authored-by: Liang-Chi Hsieh <[email protected]> Signed-off-by: Hyukjin Kwon <[email protected]>
|
Sorry guys. it was my bad. I had to wait for the test results. will be careful next time .. |
4 participants
What changes were proposed in this pull request?
Change log level of tests to WARN
Why are the changes needed?
After #34895, the log level of tests becomes either "INFO" or "DEBUG", this increases the log output file to over 100MB!
E.g https://github.com/gengliangwang/spark/runs/4623214509?check_suite_focus=true
This makes it difficult to find the CI test failures. Changing the log level of tests to WARN should help.
Does this PR introduce any user-facing change?
No
How was this patch tested?
It's just conf change.