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

[1.x][submodule] Upgrade to oneDNN v1.6.1 #18867

Merged
merged 1 commit into from
Aug 11, 2020

Conversation

bartekkuncer
Copy link
Contributor

Description

(Brief description on what this PR is about)

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 https://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
  • To the best of my knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

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

Comments

  • If this change is a backward incompatible change, why must this change be made.
  • Interesting edge cases to note here

@mxnet-bot
Copy link

Hey @bartekkuncer , 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, clang, centos-cpu, sanity, website, miscellaneous, windows-cpu, centos-gpu, unix-cpu, unix-gpu, windows-gpu]


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.

@samskalicky
Copy link
Contributor

Hi @bartekkuncer, do you want to add this oneDNN update to the v1.8 release? If so, can you mention that here in the RFC issue: #18800
Thanks!

@bartekkuncer bartekkuncer changed the title [1.x][submodule] Upgrade to official oneDNN v1.6 [1.x][submodule] Upgrade to official oneDNN v1.6.1 Aug 10, 2020
@bartekkuncer bartekkuncer changed the title [1.x][submodule] Upgrade to official oneDNN v1.6.1 [1.x][submodule] Upgrade to oneDNN v1.6.1 Aug 10, 2020
@samskalicky
Copy link
Contributor

@PatricZhao can we get someone on Intel side to review this for v1.x branch? Any anticipated issues?

Copy link
Contributor

@pengzhao-intel pengzhao-intel left a comment

Choose a reason for hiding this comment

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

LGTM

@pengzhao-intel pengzhao-intel merged commit 1711103 into apache:v1.x Aug 11, 2020
@szha szha added this to the v1.8.0 milestone Aug 23, 2020
@bartekkuncer bartekkuncer deleted the official-dnnl-v1.6 branch March 19, 2021 11:01
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants