-
Notifications
You must be signed in to change notification settings - Fork 35
ConcurrentOpenConcurrentCloseHandles
and ConcurrentGetConcurrentPutHandles
tests fail when NTHREADS == utils_get_num_cores()
#1169
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
Comments
Maybe this ASAN error has something to do with it?
|
See: #1224 |
I am not sure because the issue above is related to the allocation flow, right? |
Most probably, or the free() path. |
@vinser52 |
ConcurrentOpenConcurrentCloseHandles
and ConcurrentGetConcurrentPutHandles
tests fail when NTHREADS == utils_get_num_cores()
New version of the issue:
Environment Information
Please provide a reproduction of the bug:All 24 failed jobs in the build: https://github.com/oneapi-src/unified-memory-framework/actions/runs/15040980329?pr=1315 Linux:
Windows (locally):
How often bug is revealed:ALWAYS when |
ConcurrentOpenConcurrentCloseHandles
andConcurrentGetConcurrentPutHandles
tests fail whenNTHREADS == utils_get_num_cores()
Environment Information
Please provide a reproduction of the bug:
All 24 failed jobs in the build: https://github.com/oneapi-src/unified-memory-framework/actions/runs/15040980329?pr=1315
of the PR: #1315
Linux:
Windows (locally):
How often bug is revealed:
ALWAYS when
NTHREADS >= utils_get_num_cores()
##############################################################################
Previous version of this issue: sporadic fail in Level Zero IPC tests
sporadic fail in Level Zero IPC tests
umfLevelZeroProviderTestSuite/umfIpcTest.ConcurrentGetConcurrentPutHandles/0
Environment Information
Please provide a reproduction of the bug:
https://github.com/oneapi-src/unified-memory-framework/actions/runs/13719665034/job/38374211866?pr=1147
How often bug is revealed:
rare
The text was updated successfully, but these errors were encountered: