-
Notifications
You must be signed in to change notification settings - Fork 788
[SYCL] piextQueueCreateWithNativeHandle should not be followed by a piQueueRetain #4988
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
Conversation
…iQueueRetain Signed-off-by: Sergey V Maslov <[email protected]>
Signed-off-by: Sergey V Maslov <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you please add a unit test to sycl/unittests/
?
The fix for the failing test in precommit comes in intel/llvm-test-suite#577 |
I don't know how to write a good unit test for this. The issue was appearing as a "leak" of a queue essentially, since it's reference counter never got to 0 in this case. We have special testing (in process of being enabled by default) design to test imbalance between create/release calls with ZE_DEBUG=4 |
We can check that for a specific code( |
Signed-off-by: Sergey V Maslov <[email protected]>
@romanovvlad : please check |
Signed-off-by: Sergey V Maslov <[email protected]>
Just in case, the "Plugin/interop-level-zero.cpp" fail is expected with a fix coming in intel/llvm-test-suite#577 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, a couple of minor comments.
Should this patches be committed simultaneously? Do they depend on each other? |
The llvm-test-suite change can be committed first, the test still passes with that change. Now CI reports unrelated CUDA failures there. |
Signed-off-by: Sergey V Maslov <[email protected]>
@romanovvlad : please merge this |
Signed-off-by: Sergey V Maslov [email protected]