mbaijal opened a new pull request #10475: Change the cuda version for docs test 
   ## Description ##
   Installation Guide Nightly test is failing due to old cuda version. 
   Update the CUDA version from 7.5 to 9.0. 
   @aaronmarkham @b0noI  Can you please review soon!
   @anirudh2290 This needs to make it into 1.2 release
   NOTE: I have not updated the cuda version to 9.1 since the slaves on the 
old(nightly) CI do not have the correct nvidia drivers. These tests are being 
migrated to the official CI in the coming weeks. 
   ## Checklist ##
   ### Essentials ###
   Please feel free to remove inapplicable items for your PR.
   - [ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to 
the relevant [JIRA issue]( 
created (except PRs with tiny changes)
   - [ ] Changes are complete (i.e. I finished coding on this PR)
   - [ ] 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)
   - [ ] 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, 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$PR_ID/$BUILD_ID/index.html
   - [ ] To the my best knowledge, examples are either not affected by this 
change, or have been fixed to be compatible with this change
   ### Changes ###
   - [ ] Updated cuda from 7.5 to 9.0
   - [ ] Updated Cudnn from 5 to 7
   ## Comments ##
   - We will know whether this change fixes the nightly test as expected only 
after the PR is merged and I run the nightly test.

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:

With regards,
Apache Git Services

Reply via email to