Thanks for the reply Aaron. Once the existing Sphinx errors are fixed and
codebase is cleaned up, lets definitely revisit this and try to add a
Sphinx build into the CI pipeline so that we can prevent MXNet
documentation from breaking.
Thanks
Anirudh
On Thu, Nov 8, 2018 at 5:16 PM Aaron Markham
Hi Folks!
We got the feedback that reproducing test results on EC2 was complex and
time consuming.
I have cleaned up my personal scripts to provision a development instance:
https://cwiki.apache.org/confluence/display/MXNET/MXNet+Developer+setup+on+AWS+EC2
