-
Notifications
You must be signed in to change notification settings - Fork 423
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
failure in shm_ib/test_ucp_perf.envelope/0 #3052
Comments
@brminich seems it's without valgrind:
in case of valgrind it would have been |
ok, did not notice that. |
yosefe
added a commit
to yosefe/ucx
that referenced
this issue
Nov 22, 2018
We must not update cached tail in uct_mm_ep_flush(), because we don't execute the pending queue. As a result, we may get new send resources but not use them, so flush could return UCS_OK while there are still pending requests. Fixes openucx#3052
yosefe
added a commit
to yosefe/ucx
that referenced
this issue
Nov 24, 2018
We must not update cached tail in uct_mm_ep_flush() if there are any pending elements. We may get new send resources but not use them, so flush could return UCS_OK while there pending requests. Fixes openucx#3052
yosefe
added a commit
to yosefe/ucx
that referenced
this issue
Nov 25, 2018
We must not update cached tail in uct_mm_ep_flush() if there are any pending elements. We may get new send resources but not use them, so flush could return UCS_OK while there pending requests. Fixes openucx#3052
yosefe
added a commit
to yosefe/ucx
that referenced
this issue
Nov 25, 2018
We must not update cached tail in uct_mm_ep_flush() if there are any pending elements. We may get new send resources but not use them, so flush could return UCS_OK while there pending requests. Fixes openucx#3052
yosefe
added a commit
to yosefe/ucx
that referenced
this issue
Nov 27, 2018
We must not update cached tail in uct_mm_ep_flush() if there are any pending elements. We may get new send resources but not use them, so flush could return UCS_OK while there pending requests. Fixes openucx#3052
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Happened with valgrind here: http://hpc-master.lab.mtl.com:8080/job/hpc-ucx-pr/8264/label=hpc-test-node-upstream,worker=0/consoleFull#-853622487b816df86-9afc-46eb-984f-1a9a125d73bb
Can be related to #2089 or #2354
The text was updated successfully, but these errors were encountered: