Update build and test with mxnet 1.7.0

[sxjscience]

Test for MXNet 1.7.0 nightly to see if there are any issue.

[leezu]

I believe this 1.7.0b actually is a build of the 1.x branch.

[sxjscience]

@ciyongch We are going to test AutoGluon with MXNet 1.7. Currently, I'm using the nightly builds of 1.x but will update that to 1.7.rc0 once that's ready.

[ciyongch]

Thanks for tagging me on this @sxjscience , I'm not sure whether there'll be nightly image for v1.7.x or later v1.7.rc0. Anyway, I will keep you posted when 1.7.rc0 is announced.

[ciyongch]

Hi @sxjscience , MXNet 1.7.0.rc0 is cut off, would you mind to have a try with the latest code base? Thanks.

[sxjscience]

@ciyongch Would you know how should I try it in CI?

[ciyongch]

push an [empty] commit?

[sxjscience]

I actually mean if there is any pip package because the previous one seems to be the 1.x nightly build. I’m currently rebuilding the static pip package. Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: ciyong <notifications@github.com> Sent: Wednesday, July 8, 2020 11:44:15 PM To: awslabs/autogluon <autogluon@noreply.github.com> Cc: Xingjian SHI <xshiab@connect.ust.hk>; Mention <mention@noreply.github.com> Subject: Re: [awslabs/autogluon] [WIP] Update build and test with mxnet 1.7.0 nightly (#546) push an [empty] commit? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#546 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABHQH3WSLWQD77E5QDOX373R2VRL7ANCNFSM4OL34URQ>.

[ciyongch]

Sorry for misunderstood your requirement. Probably there's no 1.7.0.rc0 (or 1.7.x branch) pip wheel yet, ping @szha @leezu to double confirm.

[sxjscience]

@ciyongch Basically the CI fails by throwing weakref not pickleble error. It might be due to the fact the gluon block is not pickleble. But I need to investigate the root cause.

[szha]

Job PR-546-8 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-546/8/index.html

[sxjscience]

@ciyongch The CI of AutoGluon has passed after the PR in MXNet is reverted

[sxjscience]

@Jerryzcn @zhreshold @jwmueller @Innixma

We are able to pass the test with 1.7.0. Currently, I'm using the wheels built from the 1.7.x branch in MXNet:

The wheel packages used:

• CPU
  • https://autogluon-kdd-mxnet-wheels.s3-accelerate.amazonaws.com/mxnet-1.7.0b20200713-py2.py3-none-manylinux2014_x86_64.whl
• GPU + CUDA100
  • https://autogluon-kdd-mxnet-wheels.s3-accelerate.amazonaws.com/mxnet_cu100-1.7.0b20200713-py2.py3-none-manylinux2014_x86_64.whl

[Innixma]

Great! Is it ok if we wait until 1.7.0 is officially released before merging this PR?

[sxjscience]

@Innixma Yes, it's fine to wait until the official 1.7.0 so I will leave it open for now.

[zhreshold]

@sxjscience Good job, thanks for pushing this

[ciyongch]

It's great to root cause the issue, thanks @sxjscience !
Just notice apache/mxnet#18358 was already reverted. Thanks.

[szha]

Job PR-546-10 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-546/10/index.html

[szha]

Job PR-546-11 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-546/11/index.html

[szha]

Job PR-546-12 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-546/12/index.html

[szha]

Job PR-546-13 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-546/13/index.html

[Innixma]

Thanks for the quick turnaround on this fix!