Temporarily disable website builds

[KellenSunderland]

Description

Temporarily disable website builds. Work around for #13833.

Checklist

Essentials

Please feel free to remove inapplicable items for your PR.

• The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
• Changes are complete (i.e. I finished coding on this PR)
• All changes have test coverage:
• Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
• Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
• Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
• Code is well-documented:
• For user-facing API changes, API doc string has been updated.
• For new C++ functions in header files, their functionalities and arguments are documented.
• For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
• Check the API doc at http:https://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
• To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Comments

• It seems it's difficult to disable a task within this pipeline as then we don't get a status report back. As a work around I've disabled the problematic document publishing piece rather than disabling the whole task.

[KellenSunderland]

@larroy This looks like it properly disables flaky website builds. Does it look ok to you?

[marcoabreu]

Possible duplicate of #13841

@aaronmarkham for approval

[KellenSunderland]

I don't think the other projects linked can be merged due to a required test that won't complete (hence this attempt).

…

On Tue, Jan 15, 2019, 9:10 AM Marco de Abreu ***@***.*** wrote: Possible duplicate of #13841 <#13841> @aaronmarkham <https://github.com/aaronmarkham> for approval — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#13887 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHGTE95aG8QKRzrjxWIIhsevvOANEePRks5vDgtwgaJpZM4aBSsX> .

[KellenSunderland]

Autocorrect. Project should be PR*. On Tue, Jan 15, 2019, 9:14 AM kellen sunderland <[email protected] wrote:

…

I don't think the other projects linked can be merged due to a required test that won't complete (hence this attempt). On Tue, Jan 15, 2019, 9:10 AM Marco de Abreu ***@***.*** wrote: > Possible duplicate of #13841 > <#13841> > > @aaronmarkham <https://github.com/aaronmarkham> for approval > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#13887 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AHGTE95aG8QKRzrjxWIIhsevvOANEePRks5vDgtwgaJpZM4aBSsX> > . >

[larroy]

LGTM, I tried the same and status was not updated. I guess is an orthogonal issue.

[larroy]

#13841

[aaronmarkham]

Is anyone looking at the underlying problem? Why are there OS errors? I checked the results of the last 30 builds. 16 failed with this error. It fails and different points during rendering the website from the markdown files, so I don't think it's content from the markdown - which by the way, builds just fine outside of CI.

[KellenSunderland]

@larroy I think the trick is this PR just disables the flaky section. It still will report back a success to Jenkins after a simple build so it shouldn't get stuck with 'status not updated'.

@aaronmarkham Agree we should certainly look at why the failures are happening. Unless there's a trivial fix (and to my eyes there didn't appear to be) I'd recommend we disable this temporarily and investigate in parallel to unblock others.

[aaronmarkham]

Fine for now... but let's figure out the underlying issue ASAP because all this will do is let more website errors slip in, and then we'll have to dig out of that hole later.

[stu1130]

@mxnet-label-bot add [pr-awaiting-merge]
Thanks for your contribution @KellenSunderland

[larroy]

Is anyone looking at the underlying problem? Why are there OS errors? I checked the results of the last 30 builds. 16 failed with this error. It fails and different points during rendering the website from the markdown files, so I don't think it's content from the markdown - which by the way, builds just fine outside of CI.

I looked but couldn't reproduce the issue. Very difficult to diagnose without a reproduction, and with the autoscaling being enabled one can't get a hold of an instance where the job failed.