Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/4337#issuecomment-72685693
I agree that the randomization will probably make this more stable, but is
there any reason that we can't bind to 0 and figure out the ephemeral port that
was used? That might be less brittle.
I think there's another flaky Flume suite test, but it looks like it might
be unrelated to the issue addressed by this patch:
https://issues.apache.org/jira/browse/SPARK-4905
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
