Github user mateiz commented on the pull request:

    https://github.com/apache/spark/pull/2514#issuecomment-56881218
  
    If you have a test that reproduces it in 1000 runs, it's fine. I'd improve 
it by seeding a random generator with a fixed seed that you saw produce the 
problem. TimSort is deterministic, so it will always throw it in that case 
(though this may break if we change the implementation).


---
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]

Reply via email to