Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Op] Do not override specified layout in pooling (2nd PR) #9328

Merged
merged 7 commits into from
Oct 21, 2021

Conversation

ccjoechou
Copy link
Contributor

Thanks for contributing to TVM! Please refer to guideline https://tvm.apache.org/docs/contribute/ for useful information and tips. After the pull request is submitted, please request code reviews from Reviewers by @ them in the pull request thread.

@ccjoechou
Copy link
Contributor Author

@vinx13, @comaniac, @masahi:
Sorry for the trouble, I have created a new PR for this issue so that all changes are shown in one commit.
Please abandon the previous PR-#9235.
This time, if needed, for any new changes, I will following advise to: either use github GUI to do rebase-and-merge or use git pull --rebase as suggested.
Thanks,

  • Joe

@ccjoechou
Copy link
Contributor Author

FYI - a new "out_layout" attribute is added for pooling so that this field can be used by user to specify a user-specific layout for pooling op (similar to what we have for conv op); then, in the pooling.cc file, we can based on the value of out_layout to determine whether to use & stick to the user-specified layout or to use relay caller's infer layout for pooling.
4 new test cases, which use user-specified layout, are added to the test_pass_convert_op_layout.py test suite.

Copy link
Contributor

@comaniac comaniac left a comment

Choose a reason for hiding this comment

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

Otherwise LGTM.

src/relay/op/nn/pooling.cc Outdated Show resolved Hide resolved
tests/python/relay/test_pass_convert_op_layout.py Outdated Show resolved Hide resolved
@ccjoechou
Copy link
Contributor Author

ccjoechou commented Oct 19, 2021 via email

Copy link
Contributor

@comaniac comaniac left a comment

Choose a reason for hiding this comment

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

Last batch of few comments.

python/tvm/relay/op/nn/_nn.py Outdated Show resolved Hide resolved
python/tvm/relay/op/nn/_nn.py Outdated Show resolved Hide resolved
python/tvm/relay/op/nn/_nn.py Outdated Show resolved Hide resolved
Copy link
Contributor

@comaniac comaniac left a comment

Choose a reason for hiding this comment

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

LGTM.

python/tvm/relay/op/nn/_nn.py Outdated Show resolved Hide resolved
@masahi
Copy link
Member

masahi commented Oct 21, 2021

@ccjoechou Looks like you've hit a flaky CI test, please run a new job again (rebase and push).
https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/PR-9328/6/pipeline/273

@ccjoechou
Copy link
Contributor Author

@masahi: Got it and I will rebase & push to trigger a new Jenkins build & test run.

@ccjoechou
Copy link
Contributor Author

@masahi, @vinx13:
BTW, we have also installed TVM Jenkinsfile with minor adjustments in order to meet requirements of our Jenkins servers. We can't get the Unit Test - python3: i386 to pass and were seeing similar ci-test error (similar to the 273 one, e.g., setup-pythest-env.sh reaching seg fault). Any tips for us to check our setup or installation here? This Jenkins server node is a ubuntu 20.04 one.
FYI - we were able to "manually" run docker/bash.sh ci steps on another machine, a ubuntu-18.04 one, and we can run Unit Test - python3: i386 w/o problems here.
Thanks.

@masahi
Copy link
Member

masahi commented Oct 21, 2021

Yes this is a known new CI issue since this week. I've sent a PR to disable the flaky i368 test for now #9344

@masahi masahi merged commit d11bdcd into apache:main Oct 21, 2021
@masahi
Copy link
Member

masahi commented Oct 21, 2021

Thanks @ccjoechou @comaniac

ylc pushed a commit to ylc/tvm that referenced this pull request Jan 7, 2022
* [Op] Do not override specified layout in pooling (2nd PR)

* [Op] Do not override specified layout in pooling (2nd PR)

* [Op] Do not override specified layout in pooling (2nd PR)

* [Op] Do not override specified layout in pooling (2nd PR)
ylc pushed a commit to ylc/tvm that referenced this pull request Jan 13, 2022
* [Op] Do not override specified layout in pooling (2nd PR)

* [Op] Do not override specified layout in pooling (2nd PR)

* [Op] Do not override specified layout in pooling (2nd PR)

* [Op] Do not override specified layout in pooling (2nd PR)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants