Skip to content
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.

Update install-mxnet-osx-python.sh #8825

Merged
merged 6 commits into from
Jan 15, 2018
Merged

Update install-mxnet-osx-python.sh #8825

merged 6 commits into from
Jan 15, 2018

Conversation

srochel
Copy link
Contributor

@srochel srochel commented Nov 27, 2017

Fixed handling of MXNET_TAG. If not set latest from master will be cloned to local directory. If a tag is specified, that tag will be used to clone the repository.

Tested with
MXNET_TAG="1.0.0.rc0" and MXNET_TAG not set in local environment

Description

Fixed handling of MXNET_TAG. If not set latest from master will be cloned to local directory. If a tag is specified, that tag will be used to clone the repository.

Checklist

Essentials

  • [y] Passed code style checking (make lint)
  • [y] Changes are complete (i.e. I finished coding on this PR)
  • [n] All changes have test coverage
  • [n] For user-facing API changes, API doc string has been updated. For new C++ functions in header files, their functionalities and arguments are well-documented.
  • [n] To my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

  • [n] Feature1, tests, (and when applicable, API doc)
  • [n] Feature2, tests, (and when applicable, API doc)

Comments

  • change does not include check if tag in repo exists, can be further enhancement.
    I will work with Aaron to update documentation.

Fixed handling of MXNET_TAG. If not set latest from master will be cloned to local directory. If a tag is specified, that tag will be used to clone the repository.

Tested with 
MXNET_TAG="1.0.0.rc0"
Copy link
Contributor

@aaronmarkham aaronmarkham left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see a couple of minor things that could improve usability and those are commented in the specific lines.
Outside of this, there seems to be a problem with the installation in two parts, the function that returns the version may be misreporting, and when running the installation twice in the same environment, the first version remains active.

This line states the version installed at the end of the script:
https://github.com/srochel/incubator-mxnet/blob/44813dd69fd6b3e7c9b98b56a55bced7f955fbdd/setup-utils/install-mxnet-osx-python.sh#L455

My results:
The results at the end (see just below) are unexpected since the version should be master with no tag used, or whatever the last build id was, right (not 0.12.1)?

SUCCESS: MXNet test passed
SUCCESS: MXNet is successfully installed and works fine!
SUCCESS: MXNet Version is: 0.12.1
END: Test MXNet

Using your example tag, this is the return at the end, which is truncated. We lost the rc0 part.

SUCCESS: MXNet test passed
SUCCESS: MXNet is successfully installed and works fine!
SUCCESS: MXNet Version is: 1.0.0
END: Test MXNet

Then when running that same version check manually I get the older version:
(mxnet3.6) 8c8590217d26:setup-utils markhama$ echo "import mxnet as mx; print(mx.version)" | python
0.12.1

Edit: it seems that version call seems like it is misreporting because of the context switch, but either way I think it might be better to change that line 455 to read:

git describe --tags

This way you get the full representation of whatever tag was used.

echo "MXNET Tag = ${MXNET_TAG}"
echo "You can set \$MXNET_TAG to the appropriate github repo tag"
echo "If not set, the default value used is the latest version on master"
echo " "
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It tells you what version it is about to install without a y/n prompt, and I think it would be good to include that, so users now seeing that they can use an env var to switch versions they won’t have to break out of the script manually to do so (and that’s if they even notice it). Here's an example prompt.

#echo "If not set, the default value used is the latest release"
echo " "
echo "MXNET Tag = ${MXNET_TAG}"
echo "You can set \$MXNET_TAG to the appropriate github repo tag"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you provide the specific command example like export MXNET_TAG=”1.0.0.rc0”.

@piiswrong
Copy link
Contributor

@srochel Any updates?

added following modifications:
a) added selection for reporting list of available tags
b) moved the tag selection into the introduction section

open: still need to resolve proper installation of the build version
Added check if mxnet was already installed on the system (e.g. pip install), as this might interfere with the attempt to download and install a new version.
Performed manual tests, all passing. This is a final commit.
empty change to trigger build.
another dummy change to fight the CI system.
@piiswrong piiswrong merged commit 25c7232 into apache:master Jan 15, 2018
CodingCat pushed a commit to CodingCat/mxnet that referenced this pull request Jan 16, 2018
* Update install-mxnet-osx-python.sh

Fixed handling of MXNET_TAG. If not set latest from master will be cloned to local directory. If a tag is specified, that tag will be used to clone the repository.

Tested with 
MXNET_TAG="1.0.0.rc0"

* Update install-mxnet-osx-python.sh

added following modifications:
a) added selection for reporting list of available tags
b) moved the tag selection into the introduction section

open: still need to resolve proper installation of the build version

* Update install-mxnet-osx-python.sh

Added check if mxnet was already installed on the system (e.g. pip install), as this might interfere with the attempt to download and install a new version.
Performed manual tests, all passing. This is a final commit.

* Update install-mxnet-osx-python.sh

empty change to trigger build.

* Update install-mxnet-osx-python.sh

another dummy change to fight the CI system.
larroy pushed a commit to larroy/mxnet that referenced this pull request Jan 18, 2018
* Update install-mxnet-osx-python.sh

Fixed handling of MXNET_TAG. If not set latest from master will be cloned to local directory. If a tag is specified, that tag will be used to clone the repository.

Tested with 
MXNET_TAG="1.0.0.rc0"

* Update install-mxnet-osx-python.sh

added following modifications:
a) added selection for reporting list of available tags
b) moved the tag selection into the introduction section

open: still need to resolve proper installation of the build version

* Update install-mxnet-osx-python.sh

Added check if mxnet was already installed on the system (e.g. pip install), as this might interfere with the attempt to download and install a new version.
Performed manual tests, all passing. This is a final commit.

* Update install-mxnet-osx-python.sh

empty change to trigger build.

* Update install-mxnet-osx-python.sh

another dummy change to fight the CI system.
yuxiangw pushed a commit to yuxiangw/incubator-mxnet that referenced this pull request Jan 25, 2018
* Update install-mxnet-osx-python.sh

Fixed handling of MXNET_TAG. If not set latest from master will be cloned to local directory. If a tag is specified, that tag will be used to clone the repository.

Tested with 
MXNET_TAG="1.0.0.rc0"

* Update install-mxnet-osx-python.sh

added following modifications:
a) added selection for reporting list of available tags
b) moved the tag selection into the introduction section

open: still need to resolve proper installation of the build version

* Update install-mxnet-osx-python.sh

Added check if mxnet was already installed on the system (e.g. pip install), as this might interfere with the attempt to download and install a new version.
Performed manual tests, all passing. This is a final commit.

* Update install-mxnet-osx-python.sh

empty change to trigger build.

* Update install-mxnet-osx-python.sh

another dummy change to fight the CI system.
rahul003 pushed a commit to rahul003/mxnet that referenced this pull request Jun 4, 2018
* Update install-mxnet-osx-python.sh

Fixed handling of MXNET_TAG. If not set latest from master will be cloned to local directory. If a tag is specified, that tag will be used to clone the repository.

Tested with 
MXNET_TAG="1.0.0.rc0"

* Update install-mxnet-osx-python.sh

added following modifications:
a) added selection for reporting list of available tags
b) moved the tag selection into the introduction section

open: still need to resolve proper installation of the build version

* Update install-mxnet-osx-python.sh

Added check if mxnet was already installed on the system (e.g. pip install), as this might interfere with the attempt to download and install a new version.
Performed manual tests, all passing. This is a final commit.

* Update install-mxnet-osx-python.sh

empty change to trigger build.

* Update install-mxnet-osx-python.sh

another dummy change to fight the CI system.
zheng-da pushed a commit to zheng-da/incubator-mxnet that referenced this pull request Jun 28, 2018
* Update install-mxnet-osx-python.sh

Fixed handling of MXNET_TAG. If not set latest from master will be cloned to local directory. If a tag is specified, that tag will be used to clone the repository.

Tested with 
MXNET_TAG="1.0.0.rc0"

* Update install-mxnet-osx-python.sh

added following modifications:
a) added selection for reporting list of available tags
b) moved the tag selection into the introduction section

open: still need to resolve proper installation of the build version

* Update install-mxnet-osx-python.sh

Added check if mxnet was already installed on the system (e.g. pip install), as this might interfere with the attempt to download and install a new version.
Performed manual tests, all passing. This is a final commit.

* Update install-mxnet-osx-python.sh

empty change to trigger build.

* Update install-mxnet-osx-python.sh

another dummy change to fight the CI system.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants