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

Unittest of cudnnCTCLoss failed in cuda10 #19968

Closed
wanghaoshuang opened this issue Sep 24, 2019 · 3 comments
Closed

Unittest of cudnnCTCLoss failed in cuda10 #19968

wanghaoshuang opened this issue Sep 24, 2019 · 3 comments
Assignees
Labels

Comments

@wanghaoshuang
Copy link
Contributor

wanghaoshuang commented Sep 24, 2019

The unittest of warp-CTC op will fail if use_cudnn was true with cuda10. It seems that the gradients given by cudnnCTCloss is different between cuda8 and cuda10.

The cudnn kernel of warpctc has been removed in #19730. And the implement of baidu/research is enough for applications in speech or NLP fields.

But it is also necessary to check the reason of failure in cuda10.

@wanghaoshuang wanghaoshuang self-assigned this Sep 24, 2019
@AIpioneer AIpioneer added the Bug label Sep 25, 2019
@wanghaoshuang
Copy link
Contributor Author

wanghaoshuang commented Sep 27, 2019

复现方法:

执行:

python test_warpctc.py

@Jie-Fang
Copy link
Contributor

Jie-Fang commented Oct 7, 2019

I tried to reproduce this bug, and the test successed.
My env:
CUDA10 + cudnn7.2 + python3

Steps:

  1. checkout to release/1.5 branch
  2. compile
  3. add built paddle to PYTHONPATH
  4. python3 test_warpctc_op.py

The unittest ran 6 tests.

W1007 03:15:22.005301   434 device_context.cc:259] Please NOTE: device: 0, CUDA Capability: 60, Driver API Version: 10.0, Runtime API Version: 10.0
W1007 03:15:22.007037   434 device_context.cc:267] device: 0, cuDNN Version: 7.2.
......
----------------------------------------------------------------------
Ran 6 tests in 4.791s

OK

Which 7.x cudnn version do you use?

@paddle-bot-old
Copy link

Since you haven't replied for more than a year, we have closed this issue/pr.
If the problem is not solved or there is a follow-up one, please reopen it at any time and we will continue to follow up.
由于您超过一年未回复,我们将关闭这个issue/pr。
若问题未解决或有后续问题,请随时重新打开,我们会继续跟进。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants