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

[v1.x][ONNX] Fix Batchnorm spatial onnx export #18846

Merged
merged 1 commit into from
Aug 3, 2020

Conversation

ChaiBapchya
Copy link
Contributor

  • fixing spatial export for batchnorm

  • retrigger CI

  • fixing broken pylint

  • retrigger build

  • deprecating spatial attribute in exporter so default behavior of spatial=1 is conveyed

* fixing spatial export for batchnorm

* retrigger CI

* fixing broken pylint

* retrigger build

* deprecating spatial attribute in exporter so default behavior of spatial=1 is conveyed
@ChaiBapchya ChaiBapchya requested a review from szha as a code owner August 3, 2020 06:22
@mxnet-bot
Copy link

Hey @ChaiBapchya , Thanks for submitting the PR
All tests are already queued to run once. If tests fail, you can trigger one or more tests again with the following commands:

  • To trigger all jobs: @mxnet-bot run ci [all]
  • To trigger specific jobs: @mxnet-bot run ci [job1, job2]

CI supported jobs: [edge, centos-gpu, sanity, unix-gpu, clang, centos-cpu, unix-cpu, miscellaneous, website, windows-gpu, windows-cpu]


Note:
Only following 3 categories can trigger CI :PR Author, MXNet Committer, Jenkins Admin.
All CI tests must pass before the PR can be merged.

@szha szha merged commit 5db8dee into apache:v1.x Aug 3, 2020
@ChaiBapchya ChaiBapchya deleted the batchnorm_spatial_onnx_export branch August 3, 2020 20:38
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.

4 participants