GitHub user zsxwing opened a pull request:
https://github.com/apache/spark/pull/7823
[SPARK-9504][Streaming][Tests]Use eventually to fix the flaky test
The previous code uses `ssc.awaitTerminationOrTimeout(500)`. Since nobody
will stop it during `awaitTerminationOrTimeout`, it's just like `sleep(500)`.
In a super overloaded Jenkins worker, the receiver may be not able to start in
500 milliseconds. Verified this in the log of
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/39149/ There
is no log about starting the receiver before this failure. That's why
`assert(runningCount > 0)` failed.
This PR replaces `awaitTerminationOrTimeout` with `eventually` which should
be more reliable.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zsxwing/spark SPARK-9504
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/7823.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #7823
----
commit 5ba2c9975414f9d10ba89a43771857ffc35ed592
Author: zsxwing <[email protected]>
Date: 2015-07-31T08:32:57Z
Use eventually to fix the flaky test
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
