Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16498
To be clear, we're not going to commit this one test case at a time. The
best strategy is to get a logical subset working, at the least, like for a
whole module. It may entail some tricky debugging if you can't reproduce the
Jenkins failures locally, though I think I flagged some potential fixes in the
last PRs already.
To be honest I don't know that this is worth our time. It's not making the
tests better, just changing them to be more consistent -- which, as a side
effect, reveals a few tests which are a bit dependent on local[2] vs local[4]
for exact results. This isn't such a big deal.
---
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
