Jenkins build failures on v1.6

[connorgoggins]

Description

Currently, Jenkins builds are failing for v1.6 - both the branch v1.6.x and the tagged release 1.6.0.rc0. The errors can be traced to dependency-related issues with the build processes for Julia, Python, and R docs.

Error Message

For shell script output and errors for each docs build, see here. For general Jenkins build failure, see here.

To Reproduce

Copy my pipeline on the dev Jenkins instance and run it on either the branch v1.6.x or on the tag 1.6.0.rc0.

[connorgoggins]

Update: a fix for Python has been identified, still running into the R docs build issue: #17920

[connorgoggins]

@mxnet-label-bot add [Doc]

[connorgoggins]

@mxnet-label-bot add [Website]

[connorgoggins]

Update: the issue with Julia & R has been root caused and identified as a Python version problem with the Jenkins pipeline (using 2.7 instead of 3). Since changing this will take a significant amount of time and we want to make the v1.6 website available to our users as soon as possible, we will move forward with generating the v1.6 artifact without Julia & R docs as a stopgap solution and make a note of this issue for future work.

[leezu]

Could you provide more details on the Python version problem? The pipeline used to work well and there has been no change to the Python version support in the 1.6 release.

[aaronmarkham]

Could you provide more details on the Python version problem? The pipeline used to work well and there has been no change to the Python version support in the 1.6 release.

Sort of a time travel issue. 1.6 used to be fine when it was master and when the Python dependencies had not yet sunsetting Python 2. But they have now, so we must use Python 3. And bring that back from the future and apply it to v1.6.x if we want to build those docs.

[szha]

Could you provide more details on the Python version problem? The pipeline used to work well and there has been no change to the Python version support in the 1.6 release.

Sort of a time travel issue. 1.6 used to be fine when it was master and when the Python dependencies had not yet sunsetting Python 2. But they have now, so we must use Python 3. And bring that back from the future and apply it to v1.6.x if we want to build those docs.

This sounds more like a problem of dependencies not being frozen. We should be able to deduce what versions were working from a past successful run.

[aaronmarkham]

Could you provide more details on the Python version problem? The pipeline used to work well and there has been no change to the Python version support in the 1.6 release.

Sort of a time travel issue. 1.6 used to be fine when it was master and when the Python dependencies had not yet sunsetting Python 2. But they have now, so we must use Python 3. And bring that back from the future and apply it to v1.6.x if we want to build those docs.

This sounds more like a problem of dependencies not being frozen. We should be able to deduce what versions were working from a past successful run.

It's Markdown 2.1 - this is the dep that is now Python 3 only. In some previous fixes I went through and pinned dependencies. And this is what I tried to apply. Thus the error on Python 2.
This is captured here in my PR that I closed because it won't work without a significant amount of back-porting.