-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-6305][BUILD][FOLLOWUP] Some cleanups for log4j properties #34959
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
Conversation
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
This comment has been minimized.
This comment has been minimized.
dongjoon-hyun
left a comment
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.
+1, LGTM (if CI passed).
|
Thanks @dongjoon-hyun . Wait for CI. |
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
I think there is a related error in the kubernetes integration tests: It is around here: Lines 30 to 45 in 14a9d84
Switching on DEBUG for log4j initialization does not trigger the logging of the expected output. |
|
Kubernetes integration test starting |
|
Test build #146402 has finished for PR 34959 at commit
|
|
Hmm, I changed the log4j properties file for the k8s integration test. But seems the test still cannot get the log4j 2 configuration file. Not sure why now. I will merge this first and keep looking at the k8s integration test issue. |
|
Kubernetes integration test status failure |
|
Test build #146406 has finished for PR 34959 at commit
|
|
Jenkins tests were passed. Thanks for reviewing. Merging to master. |
|
@viirya It seems that test failure still exists in https://amplab.cs.berkeley.edu/jenkins/job/spark-master-test-maven-hadoop-3.2/3527/consoleFull |
|
Which one you mean? I don't see failed test in test results. |
|
|
I will try to reproduce it locally. |
|
And there are some error log as follows: It seems that there is some thing wrong with log4j2 configuration. |
|
The log4j error I have seen locally, but it doesn't affect SBT test. Not sure if it is related. |
ok |
|
Do you see other issues? Seems other tests are all passed on maven, right? |
It seems so, only |
| |appender.console.layout.type = PatternLayout | ||
| |appender.console.layout.pattern = %d{yy/MM/dd HH:mm:ss} %p %c{1}: %m%n | ||
| """.stripMargin, | ||
| new File(s"$tempLog4jConf/log4j.properties"), |
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.
change new File(s"$tempLog4jConf/log4j.properties") to new File(s"$tempLog4jConf/log4j2.properties"), then HiveThriftBinaryServerSuite no longer hang
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.
However, it seems that all logs are printed to the console, which is different from the previous behavior
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.
SBT cannot reproduce it. But we should use log4j2.properties.
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 corrected this together in #34965.
This is a followup of SPARK-6305. Some places in build files (maven and sbt) which remove log4j properties files should be updated. Some tests programmingly write log4j properties should be updated to log4j 2 syntax too. To clean up build files and migrate some tests to log4j2 syntax. No Pass all tests. Closes apache#34959 from viirya/log4j2_followup. Authored-by: Liang-Chi Hsieh <[email protected]> Signed-off-by: Liang-Chi Hsieh <[email protected]>
### What changes were proposed in this pull request? This is a followup of SPARK-6305. Some places in build files (maven and sbt) which remove log4j properties files should be updated. Some tests programmingly write log4j properties should be updated to log4j 2 syntax too. ### Why are the changes needed? To clean up build files and migrate some tests to log4j2 syntax. ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? Pass all tests. Closes apache#34959 from viirya/log4j2_followup. Authored-by: Liang-Chi Hsieh <[email protected]> Signed-off-by: Liang-Chi Hsieh <[email protected]>
### What changes were proposed in this pull request? This is a followup of SPARK-6305. Some places in build files (maven and sbt) which remove log4j properties files should be updated. Some tests programmingly write log4j properties should be updated to log4j 2 syntax too. ### Why are the changes needed? To clean up build files and migrate some tests to log4j2 syntax. ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? Pass all tests. Closes apache#34959 from viirya/log4j2_followup. Authored-by: Liang-Chi Hsieh <[email protected]> Signed-off-by: Liang-Chi Hsieh <[email protected]> (cherry picked from commit 9f6062a)
What changes were proposed in this pull request?
This is a followup of SPARK-6305. Some places in build files (maven and sbt) which remove log4j properties files should be updated. Some tests programmingly write log4j properties should be updated to log4j 2 syntax too.
Why are the changes needed?
To clean up build files and migrate some tests to log4j2 syntax.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Pass all tests.