zhengruifeng opened a new pull request, #37097:
URL: https://github.com/apache/spark/pull/37097

   ### What changes were proposed in this pull request?
   Skip flaky doctests
   
   
   ### Why are the changes needed?
   ```
   File "/__w/spark/spark/python/pyspark/mllib/linalg/distributed.py", line 
859, in __main__.IndexedRowMatrix.computeSVD
   Failed example:
       svd_model.V # doctest: +ELLIPSIS
   Expected:
       DenseMatrix(3, 2, [-0.4082, -0.8165, -0.4082, 0.8944, -0.4472, 0.0], 0)
   Got:
       DenseMatrix(3, 2, [-0.4082, -0.8165, -0.4082, 0.8944, -0.4472, -0.0], 0)
   **********************************************************************
   File "/__w/spark/spark/python/pyspark/mllib/linalg/distributed.py", line 
426, in __main__.RowMatrix.computeSVD
   Failed example:
       svd_model.V # doctest: +ELLIPSIS
   Expected:
       DenseMatrix(3, 2, [-0.4082, -0.8165, -0.4082, 0.8944, -0.4472, 0.0], 0)
   Got:
       DenseMatrix(3, 2, [-0.4082, -0.8165, -0.4082, 0.8944, -0.4472, -0.0], 0)
   **********************************************************************
      1 of   6 in __main__.IndexedRowMatrix.computeSVD
      1 of   6 in __main__.RowMatrix.computeSVD
   ***Test Failed*** 2 failures.
   Had test failures in pyspark.mllib.linalg.distributed with python3.9; see 
logs.
   ```
   
   https://github.com/apache/spark/pull/37002 occasionally cause above tests 
output `-0.0` instead of `0.0`, I think they are both acceptable.
   
   
   ### Does this PR introduce _any_ user-facing change?
   No
   
   
   ### How was this patch tested?
   updated doctests
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to