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

[QST]nvcompStatus_t nvcompErrorInvalidValue #99

Open
TonyTong999 opened this issue Mar 4, 2024 · 4 comments
Open

[QST]nvcompStatus_t nvcompErrorInvalidValue #99

TonyTong999 opened this issue Mar 4, 2024 · 4 comments
Labels
? - Needs Triage inactive-30d question Further information is requested

Comments

@TonyTong999
Copy link

I encountered nvcompErrorInvalidValue when using nvcompBatchedANSCompressAsync. I want to know what value in specific is invalid, and how should I debug

@TonyTong999 TonyTong999 added ? - Needs Triage question Further information is requested labels Mar 4, 2024
Copy link

github-actions bot commented Apr 4, 2024

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.

Copy link

github-actions bot commented Jul 3, 2024

This issue has been labeled inactive-90d due to no recent activity in the past 90 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed.

@BeeBreeze
Copy link

BeeBreeze commented Oct 21, 2024

same issue. I encounter with this problem while using benchmark_ans_chunked.
with Driver version 560.76, CUDA version 12.6.68, compressing the CMakelists.txt can reproduce the bug.

Copy link

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
? - Needs Triage inactive-30d question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants