-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
[WIP] ZEPPELIN-1761. CI: ZeppelinSparkClusterTest .pySpark* fail the build #1765
Closed
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
zjffdu
force-pushed
the
ZEPPELIN-1761
branch
from
December 15, 2016 08:08
40bdf30
to
8030119
Compare
zjffdu
force-pushed
the
ZEPPELIN-1761
branch
4 times, most recently
from
December 16, 2016 00:16
57d1ef0
to
4348f49
Compare
This PR is not ready for review, I just add more logging to reproduce it in CI. |
zjffdu
force-pushed
the
ZEPPELIN-1761
branch
3 times, most recently
from
December 16, 2016 12:02
bbab343
to
6f7c589
Compare
could you mark the title with [WIP]? |
zjffdu
changed the title
ZEPPELIN-1761. CI: ZeppelinSparkClusterTest .pySpark* fail the build
[WIP] ZEPPELIN-1761. CI: ZeppelinSparkClusterTest .pySpark* fail the build
Dec 19, 2016
zjffdu
force-pushed
the
ZEPPELIN-1761
branch
2 times, most recently
from
December 19, 2016 14:17
cea76c0
to
5aaf4f5
Compare
zjffdu
force-pushed
the
ZEPPELIN-1761
branch
3 times, most recently
from
December 20, 2016 13:25
bd4f2e3
to
5cce03c
Compare
where are we on this? |
Didn't see the error recently, let me try again. |
I had similar issue a week ago: |
asfgit
pushed a commit
that referenced
this pull request
May 9, 2018
close #83 close #86 close #125 close #133 close #139 close #146 close #193 close #203 close #246 close #262 close #264 close #273 close #291 close #299 close #320 close #347 close #389 close #413 close #423 close #543 close #560 close #658 close #670 close #728 close #765 close #777 close #782 close #783 close #812 close #822 close #841 close #843 close #878 close #884 close #918 close #989 close #1076 close #1135 close #1187 close #1231 close #1304 close #1316 close #1361 close #1385 close #1390 close #1414 close #1422 close #1425 close #1447 close #1458 close #1466 close #1485 close #1492 close #1495 close #1497 close #1536 close #1545 close #1561 close #1577 close #1600 close #1603 close #1678 close #1695 close #1739 close #1748 close #1765 close #1767 close #1776 close #1783 close #1799
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 is this PR for?
Add more logging as I could not reproduce it locally.
What type of PR is it?
[ Improvement ]
Todos
What is the Jira issue?
How should this be tested?
Outline the steps to test the PR here.
Screenshots (if appropriate)
Questions: