{"push_id":3158800530,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"9b01d655394f312c5271ede644c701d3566983f8","before":"9e1edc77ee59ce6ad2a06d9aefb3a8d863df0fb1","commits":[{"sha":"dc01f5189ada13f3b89f9b5ef3c7ad5ed48c9c6b","author":{"name":"Dmitry Gladkov","email":"5d505d2896a31d38758db64cec3ee196962c6e6e@intel.com"},"message":"prov/rxm: Fix lack of MSG CQ progress\n\nMost of OFI applications implemnts send-progress-retry logic in case of\n`fi_send`/`fi_inject` operations returns -FI_EAGAIN.\nSome of them don't provide the buffer(s) for completions (i.e.\n`fi_cq_[s]read` with `count` = 0), because they don't know how to handle\nunexpected completions.\nIf there is at least one CQ entry (for the previous operations) in circular\nqueue (utility CQ storage for the completions that ready to read by user)\nand such application calls handles -FI_EAGAIN from `fi_send`/`fi_inject` with\n`fi_cq_read(..., count = 0)`, it leads to hang in this send-progress-retry..\n\nSigned-off-by: Dmitry Gladkov <dmitry.gladkov@intel.com>","distinct":true,"url":"https://api.github.com/repos/SystemFabricWorks/libfabric/commits/dc01f5189ada13f3b89f9b5ef3c7ad5ed48c9c6b"},{"sha":"9b01d655394f312c5271ede644c701d3566983f8","author":{"name":"Sean Hefty","email":"9575f92314b8ac7581ac1b2afb880058b7fbd431@intel.com"},"message":"Merge pull request #4700 from dmitrygladkov/rxm_conn\n\nprov/rxm: Fix lack of MSG CQ progress","distinct":true,"url":"https://api.github.com/repos/SystemFabricWorks/libfabric/commits/9b01d655394f312c5271ede644c701d3566983f8"}]}
{"actor":{"display_login":"ofi-cray-test"}}