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

Build from source, rnnt_loss_test_py Failed #1191

Open
tomato18463 opened this issue May 11, 2023 · 6 comments
Open

Build from source, rnnt_loss_test_py Failed #1191

tomato18463 opened this issue May 11, 2023 · 6 comments

Comments

@tomato18463
Copy link

tomato18463 commented May 11, 2023

My system is Ubuntu 18.04, CUDA 11.8, pytorch 2.0.0. I built k2 from source, it worked well. Then I run the test case as instructed here. I have all test cases passed but rnnt_loss_test_py failed. I have attached the test log below.

Please can you have a look at what's wrong? Is it a problem with my system? Would it influence normal use of k2, and if yes, how to fix it?

Thanks!

LastTest.log

@yfyeung
Copy link
Contributor

yfyeung commented May 11, 2023

You can change test_rnnt_loss_empty_reference to _test_rnnt_loss_empty_reference to disable this test.

@tomato18463
Copy link
Author

Will it cause some errorous result in some specific function if I ignore this test? Is there any function I should avoid with this test failed?

You can change test_rnnt_loss_empty_reference to _test_rnnt_loss_empty_reference to disable this test.

@yfyeung
Copy link
Contributor

yfyeung commented May 11, 2023

Currently, we didn't find any errorous results caused by rnn_loss.py.
When S is 0, torchaudio.functional.rnnt_loss gets non-zeros value, which is different with k2.rnnt_loss.

@tomato18463
Copy link
Author

Currently, we didn't find any errorous results caused by rnn_loss.py.

I see. Thanks!

@tomato18463
Copy link
Author

Is it this line that I need to change?

@yfyeung
Copy link
Contributor

yfyeung commented May 11, 2023

Is it this line that I need to change?

You can refer this PR: #1193

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

No branches or pull requests

2 participants