[Do not merge] This PR (v2) is for check the fix in onDNN.

[pioy]

This PR is for check the fix in onDNN (see #19251).
I additionally added a piece of code that make a lot of test failing without the fix.
If the tests passes then the fix works despite the code that introduce failing stimulus (which previously caused fails).

[mxnet-bot]

Hey @pioy , 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: [sanity, centos-gpu, website, windows-cpu, unix-cpu, clang, centos-cpu, edge, miscellaneous, 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.

[pioy]

@mxnet-bot run ci centos-cpu

[mxnet-bot]

Undefined action detected.
Permissible actions are : run ci [all], run ci [job1, job2]
Example : @mxnet-bot run ci [all]
Example : @mxnet-bot run ci [centos-cpu, clang]

[pioy]

@mxnet-bot run ci [centos-cpu]

[pioy]

@mxnet-bot run ci [centos-cpu]

[mxnet-bot]

Jenkins CI successfully triggered : [centos-cpu]

[pioy]

@mxnet-bot run ci [unix-cpu]

[mxnet-bot]

Jenkins CI successfully triggered : [unix-cpu]

[pioy]

@mxnet-bot run ci [centos-cpu]

[mxnet-bot]

Jenkins CI successfully triggered : [centos-cpu]

[pioy]

It looks like I missed something switching to my onDNN repo which, in fact, did not happen.