Skip to content
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

Investigate why test fixtures go 💥 if we have more than one TEST in a single process. #159

Open
arjo129 opened this issue Feb 16, 2022 · 4 comments
Labels
bug Something isn't working

Comments

@arjo129
Copy link
Member

arjo129 commented Feb 16, 2022

Google protobuf doesn't like the way we are linking the messages in our repository. Whenever we try to run two TestFixtures in the same process the tests will segfault.

@hidmic hidmic added the bug Something isn't working label May 19, 2022
@hidmic
Copy link
Collaborator

hidmic commented May 19, 2022

protocolbuffers/protobuf#4126 suggests loading/unloading protobuf message shared libraries leaves bad global state behind. Perhaps we can preload them?

@arjo129
Copy link
Member Author

arjo129 commented Sep 8, 2022

Hopefully eventually we can move away from custom messages then?

@marcoag
Copy link
Member

marcoag commented Sep 8, 2022

In general running two servers in the same test seems to be troublesome with gazebo. Dunno if its the same issue but I also had troubles trying to run two servers in the same test file in gz-sim so I have to split them in two files (here and here).

@hidmic
Copy link
Collaborator

hidmic commented Nov 10, 2022

We know why this happens and it's very much core to how protobuf works. I'm inclined to close this as wont fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants