-
Notifications
You must be signed in to change notification settings - Fork 28.1k
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-3490] Disable SparkUI for tests (backport into 1.0) #3959
Conversation
Test build #25274 has started for PR 3959 at commit
|
Test build #25274 has finished for PR 3959 at commit
|
Test FAILed. |
retest this please |
Test build #25330 has started for PR 3959 at commit
|
Test build #25330 has finished for PR 3959 at commit
|
Test FAILed. |
Looks like the context cleaner suite is consistently failing. (It's failing outside of this PR too) |
Ok, I have cherry-picked those commits, though they shouldn't affect the particular test that has been failing ( |
Test build #25345 has started for PR 3959 at commit
|
Test build #25345 has finished for PR 3959 at commit
|
Test FAILed. |
Jenkins, retest this please. |
Test build #25436 has started for PR 3959 at commit
|
Test build #25436 has finished for PR 3959 at commit
|
Test FAILed. |
Jenkins, retest this please. |
Test build #25613 has started for PR 3959 at commit
|
Test build #25613 has finished for PR 3959 at commit
|
Test FAILed. |
I logged into Jenkins to look at the
and
Kind of hard to figure out which tests were hitting this (since we don't have any helpful Log4J messages to let us know which test was running when log messages were written), but I'm going to assume that this is the failed test. Looks like maybe this is a path / environment variable / CWD issue. I'll investigate. |
Interesting. Thanks for looking into this more @JoshRosen. This looks a lot like a Spark home issue that I've seen in the past, where the executors on different machines inherit the same Spark home from the driver and use this Spark home to call |
Whats the state of this PR? Is it still relevant? |
yes, the tests are still not passing I believe, test this please |
Test build #26933 has started for PR 3959 at commit
|
Test build #26933 has finished for PR 3959 at commit
|
Test FAILed. |
Jenkins, retest this please. |
Test build #27032 has started for PR 3959 at commit
|
Test build #27032 has finished for PR 3959 at commit
|
Test FAILed. |
Branch-1.2 #2363 (original)
Branch-1.1 #2415
Branch-1.0 #3959 (this PR)
Branch-0.9 #3961