mxnet
mxnet copied to clipboard
[BUGFIX] Fix some typos.
Description
(Brief description on what this PR is about) Fix some typos in cd/, ci/, cpp-package/, example/, include/, licenses/, tools/, tests/.
Checklist
Essentials
- [x] PR's title starts with a category (e.g. [BUGFIX], [MODEL], [TUTORIAL], [FEATURE], [DOC], etc)
- [x] Changes are complete (i.e. I finished coding on this PR)
- [ ] All changes have test coverage
- [x] Code is well-documented
Changes
- [ ] Feature1, tests, (and when applicable, API doc)
- [ ] Feature2, tests, (and when applicable, API doc)
Comments
- If this change is a backward incompatible change, why must this change be made.
- Interesting edge cases to note here
Hey @Yulv-git , Thanks for submitting the PR All tests are already queued to run once. If tests fail, you can trigger one or more tests again with the following commands:
- To trigger all jobs: @mxnet-bot run ci [all]
- To trigger specific jobs: @mxnet-bot run ci [job1, job2]
CI supported jobs: [unix-gpu, unix-cpu, windows-cpu, windows-gpu, miscellaneous, website, edge, centos-gpu, sanity, centos-cpu, clang]
Note: Only following 3 categories can trigger CI :PR Author, MXNet Committer, Jenkins Admin. All CI tests must pass before the PR can be merged.
Hi, thanks for the contributions. We had some issues with our CI recently. Can you please merge in the latest changes from the master branch into your PR?
Hi, thanks for the contributions. We had some issues with our CI recently. Can you please merge in the latest changes from the master branch into your PR?
I have merged the latest master branch into the branch where the current RP is.