barry-jin opened a new pull request #20138: URL: https://github.com/apache/incubator-mxnet/pull/20138
## Description ## Looks like in some PRs, code coverage report will be submitted to some unknown places, like: https://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Fcentos-cpu/detail/PR-20105/8/pipeline/173/ Commit head is 622f0b3, but the report will be submitted to https://codecov.io/github/apache/incubator-mxnet/commit/395b8c9c168e7941c9d96e3a4a1328783cc72956 https://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-cpu/detail/PR-20107/4/pipeline/295 Commit head is cab1562, but the report will be submitted to https://codecov.io/github/apache/incubator-mxnet/commit/b5b7dbc2374ceb7b595943b8d13abd60ba32841b So, this PR will add codecovArgs back. ## 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) - [x] 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 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
