Skip to content
This repository has been archived by the owner on Sep 5, 2023. It is now read-only.

MT-test failed, maybe a synchro issue in the MT-framework? #1079

Closed
ldorau opened this issue Jun 2, 2021 · 4 comments
Closed

MT-test failed, maybe a synchro issue in the MT-framework? #1079

ldorau opened this issue Jun 2, 2021 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@ldorau
Copy link
Member

ldorau commented Jun 2, 2021

MT-test failed:
https://app.circleci.com/pipelines/github/pmem/rpma/194/workflows/74f049b3-b477-4ccc-8d1d-82883a9fed66/jobs/199

Maybe a synchro issue in the MT-framework?

@ldorau
Copy link
Member Author

ldorau commented Jun 2, 2021

@janekmi

@yangx-jy
Copy link
Contributor

yangx-jy commented Jun 15, 2021

@ldorau @janekmi

It seems that mt-framework lacks process synchronization because fork() cannot determine the execution order of (parent & child) processes. We need to finish rdma_listen() in child before running rdma_connect in parent by some mechanisms (e.g. futex, semaphore, signal? not sure which one is the best).

@janekmi
Copy link

janekmi commented Jul 26, 2021

You are right @yangx-jy. I think the easier way is to provide an interprocess-synchronization based on semaphores. I have proposed a very rough proof of concept. But it requires some additional work to become an elegant solution.

As for now, I recommend turning off all tests that have sneaked into our CI introducing this issue.

Ref: #1050

@ldorau
Copy link
Member Author

ldorau commented Aug 25, 2022

Fixed by #1604 and #1635

@ldorau ldorau closed this as completed Aug 25, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants