aaronmarkham commented on issue #16146: Website build on CI is down due to Julia error URL: https://github.com/apache/incubator-mxnet/issues/16146#issuecomment-583906642 So it worked for me on my test. Not sure why exactly, but I ended up with slightly older versions of things. From my log: ``` mkdocs==1.0.4 mkdocs-material==4.6.0 pymdown-extensions==6.2.1 python-markdown-math==0.6 ``` I think maybe adding these will do the trick. Considering that my current setup isn't failing, I'm not entirely sure how to test this out, but it's worth a try. ## Side note Now, I tried to run `pip freeze` but the Docker image that I had left was (I guess) before these things ran. The logs state: ``` 2020-02-08 00:43:31,273 - root - INFO - Waiting for status of container 73b619cf6eea for 600 s. 2020-02-08 00:43:31,467 - root - INFO - Container exit status: {'Error': None, 'StatusCode': 0} 2020-02-08 00:43:31,467 - root - INFO - Container exited with success 👍 2020-02-08 00:43:31,467 - root - INFO - Executed command for reproduction: ci/build.py --docker-registry mxnetci --platform ubuntu_cpu_julia /work/runtime_functions.sh build_julia_docs 2020-02-08 00:43:31,468 - root - INFO - Stopping container: 73b619cf6eea 2020-02-08 00:43:31,469 - root - INFO - Removing container: 73b619cf6eea ``` So it removed what I had as a working state. How unfortunate! Anyone know what flag (or whatever) I could have set when running build.py so that I'd get to keep the last version of the container around for testing?
---------------------------------------------------------------- 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] With regards, Apache Git Services
