-
Notifications
You must be signed in to change notification settings - Fork 28.3k
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-19597][CORE] test case for task deserialization errors #16930
Conversation
Test build #72880 has finished for PR 16930 at commit
|
Jenkins, retest this please |
Test build #72891 has finished for PR 16930 at commit
|
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.
One small comment -- otherwise looks good
val conf = new SparkConf | ||
val serializer = new JavaSerializer(conf) | ||
val env = createMockEnv(conf, serializer) | ||
val serializedTask = serializer.newInstance().serialize(new NonDeserializableTask) |
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.
can you take the error message as a param to NonDeserializableTask, so the magic string can be defined once and used below on line 137? From a quick read I thought the one on line 137 was coming from the Spark core code (not from the test code)
LGTM assuming tests pass |
Test build #73437 has finished for PR 16930 at commit
|
I merged this into master |
thanks @kayousterhout ! |
Adds a test case that ensures that Executors gracefully handle a task that fails to deserialize, by sending back a reasonable failure message. This does not change any behavior (the prior behavior was already correct), it just adds a test case to prevent regression. Author: Imran Rashid <irashid@cloudera.com> Closes apache#16930 from squito/executor_task_deserialization.
Adds a test case that ensures that Executors gracefully handle a task that fails to deserialize, by sending back a reasonable failure message. This does not change any behavior (the prior behavior was already correct), it just adds a test case to prevent regression.