Skip to content
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.

Commit

Permalink
Updated documentation about nightly tests (#14493)
Browse files Browse the repository at this point in the history
* 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]>
  • Loading branch information
lebeg authored and aaronmarkham committed Apr 3, 2019
1 parent b482a44 commit 28fe552
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions tests/nightly/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down

0 comments on commit 28fe552

Please sign in to comment.