mseth10 opened a new pull request #14016: fix test_depthwise_convoltuion for 
occasional CI failures
URL: https://github.com/apache/incubator-mxnet/pull/14016
 
 
   ## Description ##
   This PR aims to fix #12203 . The test_depthwise convolution fails 
occasionally on CI for GPU context. The problem occurs as the test tries to 
match **GPU** output of convolution on an image with **CPU** output of 
convolution on sliced images concatenated later. The error tolerance values are 
sometimes exceeded. When the comparison instead is made between **GPU** output 
of convolution on an image with **GPU** output of convolution on sliced images 
concatenated later, it passes the test.
   
   ## Checklist ##
   ### Essentials ###
   Please feel free to remove inapplicable items for your PR.
   - [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] Second context changed to match first one. This make comparison for 
different implementations on same contexts
   
   ## Comments ##
   - If this change is a backward incompatible change, why must this change be 
made.
   - Interesting edge cases to note here
   

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