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
[SPARK-47112][INFRA] Write logs into a file in SparkR Windows build #45192
Closed
+1
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
HyukjinKwon
force-pushed
the
reduce-logs
branch
from
February 21, 2024 06:35
235dbbc
to
87607c5
Compare
BTW, I know why it shows an error like:
which is actually a warning. I will make a separate fix: #45196 |
This should be good to go. |
LuciferYang
approved these changes
Feb 21, 2024
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.
LGTM
Merged to master. |
+1, LGTM. |
ericm-db
pushed a commit
to ericm-db/spark
that referenced
this pull request
Mar 5, 2024
### What changes were proposed in this pull request? We used to write Log4J logs into `target/unit-tests.log` instead of console. This seems to be broken in SparkR Windows job. This PR fixes it. ### Why are the changes needed? https://github.com/apache/spark/actions/runs/7977185456/job/21779508822#step:10:89 This write too many logs, and difficult to see the real test cases. ### Does this PR introduce _any_ user-facing change? No, dev-only. ### How was this patch tested? In my fork ### Was this patch authored or co-authored using generative AI tooling? No. Closes apache#45192 from HyukjinKwon/reduce-logs. Authored-by: Hyukjin Kwon <gurwls223@apache.org> Signed-off-by: Hyukjin Kwon <gurwls223@apache.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
We used to write Log4J logs into
target/unit-tests.log
instead of console. This seems to be broken in SparkR Windows job. This PR fixes it.Why are the changes needed?
https://github.com/apache/spark/actions/runs/7977185456/job/21779508822#step:10:89
This write too many logs, and difficult to see the real test cases.
Does this PR introduce any user-facing change?
No, dev-only.
How was this patch tested?
In my fork
Was this patch authored or co-authored using generative AI tooling?
No.