Github user jose-torres commented on the issue:

    https://github.com/apache/spark/pull/20225
  
    The problem in the test runs above was also a test issue. The new code 
changed the synchronization such that the row wasn't written when the test 
expected; I verified manually that the failing test doesn't actually enter the 
attemptNumber != 0 branch.


---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to