haojin2 opened a new pull request #12557: Fix for flaky 
test_operator_gpu.test_spatial_transformer_with_type
URL: https://github.com/apache/incubator-mxnet/pull/12557
 
 
   ## Description ##
   Fix for #11839.
   
   ## Checklist ##
   ### Essentials ###
   - [x] Changes are complete (i.e. I finished coding on this PR)
   - [x] All changes have test coverage:
   - Unit tests are added for small changes to verify correctness (e.g. adding 
a new operator)
   - Nightly tests are added for complicated/long-running ones (e.g. changing 
distributed kvstore)
   - Build tests will be added for build configuration changes (e.g. adding a 
new build option with NCCL)
   - [x] Code is well-documented: 
   - For user-facing API changes, API doc string has been updated. 
   - For new C++ functions in header files, their functionalities and arguments 
are documented. 
   - For new examples, README.md is added to explain the what the example does, 
the source of the dataset, expected performance on test set and reference to 
the original paper if applicable
   - Check the API doc at 
http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
   - [x] To the my best knowledge, examples are either not affected by this 
change, or have been fixed to be compatible with this change
   
   ### Changes ###
   - [x] Add `cudnn_off` parameter to SpatialTransformer
   - [x] Fix the inconsistency between CPU & GPU implementation
   
   ## Comments ##
   New test passed more than 10000 times
   ```
   MXNET_TEST_COUNT=10000 nosetests -s --verbose 
tests/python/gpu/test_operator_gpu.py:test_spatial_transformer_with_type
   [INFO] Setting module np/mx/python random seeds, use 
MXNET_MODULE_SEED=2123178900 to reproduce.
   test_operator_gpu.test_spatial_transformer_with_type ... ok
   
   ----------------------------------------------------------------------
   Ran 1 test in 452.145s
   
   OK
   ```

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to