mbaijal opened a new pull request #10827: [MXNET-405][WIP] Add 2 new pipelines to the Official CI and run nightly tests. URL: https://github.com/apache/incubator-mxnet/pull/10827 ## Description ## @marcoabreu @gautamkmr Can you please review ! This PR does the following: 1. Added 2 new Jenkins pipeline jobs - one which runs tests on MXNet Source and other which runs tests on MXNet Binaries. 2. Several tests were running nightly on a local jenkins setup. I have modified these tests to the new format so they now run as a part of the new jenkinsfiles on the official CI 3. I have not modified any tests themselves but have only modified the design/format so that they run as a pipeline 4. This provides an easy mechanism for any one to add long running tests to run as a part of the nightly pipelines. While reviewing this code, you can look at this link where these pipelines are currently running on my local repo: http://jenkins.mxnet-ci.amazon-ml.com/view/Nightly%20Tests/ ## Checklist ## ### Essentials ### Please feel free to remove inapplicable items for your PR. - [x] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant [JIRA issue](https://issues.apache.org/jira/projects/MXNET/issues) created (except PRs with tiny changes) - [ ] 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] Created a new Jenkinsfile to run nightly tests on source - [x] Created a new Jenkinsfile to run nightly tests on mxnet binaries - [x] Made some changes to a few test scripts to make them compatible with the new CI design (Image classification, compilation warnings, Installation guide etc) - [x] Added RAT check as a nightly test with a post run check on the logs - [x] Added new dockerfiles for some tests as needed (for example the JS test and Install guide) - [x] Added appropriate install scripts where needed for the newly added dockerfiles - [ ] Added Readmes/comments where necessary - [x] Fix Pip Install test - [ ] Add an instance with 4 GPUs and then uncomment the KVstore test ## Comments ## To the best of my knowledge, the 3 tests that I have changed are not being run elsewhere/ standalone and hence should not cause any regressions. To Do: 1. Need to remove pip test from the source pipeline - it is deprecated 2. There is a potential install issue that I need to test (build from source on a cpu only instance)
---------------------------------------------------------------- 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
