sandeep-krishnamurthy opened a new pull request #11902: Remove stale unused Keras1-MXNet tests from MXNet repo URL: https://github.com/apache/incubator-mxnet/pull/11902 ## Description ## * Remove all stale and deprecated Keras1.2 with MXNet tests and cleaning up. * Keras 1.2.1 with MXNet backend is no more supported and deprecated - https://github.com/dmlc/keras/ * Most recent release and active development is happening for Keras2 with MXNet backend - https://github.com/awslabs/keras-apache-mxnet * Keras2-MXNet has is own CI and build pipelines. ## 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](https://issues.apache.org/jira/projects/MXNET/issues) created (except PRs with tiny changes) - [X] 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, 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 ### - Removing obsolete unused Keras1-MXNet tests from MXNet repo ## Comments ## N/A @marcoabreu @roywei
---------------------------------------------------------------- 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
