This is an automated email from the ASF dual-hosted git repository.
aaronmarkham pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-mxnet.git
The following commit(s) were added to refs/heads/master by this push:
new 28fe552 Updated documentation about nightly tests (#14493)
28fe552 is described below
commit 28fe5521b348c6ffe21ab56a70d1199dd9bbee13
Author: Anton Chernov <[email protected]>
AuthorDate: Wed Apr 3 20:28:55 2019 +0200
Updated documentation about nightly tests (#14493)
* Updated documentation about nightly tests
* Update tests/nightly/README.md
Co-Authored-By: lebeg <[email protected]>
* Update tests/nightly/README.md
Co-Authored-By: lebeg <[email protected]>
* Update tests/nightly/README.md
Co-Authored-By: lebeg <[email protected]>
---
tests/nightly/README.md | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/tests/nightly/README.md b/tests/nightly/README.md
index 774a975..bc483d2 100644
--- a/tests/nightly/README.md
+++ b/tests/nightly/README.md
@@ -17,16 +17,16 @@
# Nightly Tests for MXNet
-These are some longer running tests that are scheduled to run every night.
+These are some longer running tests that are scheduled to run every night, for
master and for latest release branches.
### Description
There are two Jenkins pipelines that run these tests -
-1. Tests on the Source code:
http://jenkins.mxnet-ci.amazon-ml.com/view/Nightly%20Tests/job/NightlyTests_onSource/
-2. Tests on Built Binaries:
http://jenkins.mxnet-ci.amazon-ml.com/view/Nightly%20Tests/job/NightlyTests_onBinaries/
+1. [Tests on source
code](http://jenkins.mxnet-ci.amazon-ml.com/job/NightlyTests/)
+2. [Tests on built
binaries](http://jenkins.mxnet-ci.amazon-ml.com/job/NightlyTestsForBinaries/)
### Adding a new Nightly Test
-Add your test script to the mxnet repo (preferably)in the tests/nightly folder)
-Make sure to describe in a readme or comments the purpose of the test.
+Add your test script to the MXNet repo's `tests/nightly/` folder. Make sure to
describe in a readme or in the
+comments the purpose of the test.
#### Setting up the Docker Container
1. Your test must run on the CI slaves only within an official docker
container available at ci/docker
