-
Notifications
You must be signed in to change notification settings - Fork 38
Test that Rust and C++ ipc_bridge example work with each other #39
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
base: main
Are you sure you want to change the base?
Conversation
|
test is locally still unstable. Sometimes service discovery does not work UPDATE fixed with latest rebase |
|
Even when tests should run serialized via using tags, I see crashes. Following command may trigger failures UPDATE fixed with latest rebase |
602cece to
78ed8a2
Compare
6b566d8 to
3cc07f7
Compare
d2e7de9 to
3710b44
Compare
3710b44 to
00249e7
Compare
51b515c to
4be07b3
Compare
|
Instead of using a shell script we should use a test framework. @draganbjedov, I'm not sure whether SCTF/ITF is far enough in S-CORE to support this? Could you please take a look? |
Using `--help` lead definitely to a crash, which should not happen, because `--help` is normal behavior. Also `main()` was missing a return statement which is ok in C/C++, but we have no control of the return value in this case. Now it is always 0, when terminating without errors.
CI should check that C++ and Rust code can communicate via mw::com to avoid having surprise regressions.
There is no Windows specific devcontainer anymore and all can use the same devcontainer.
0fe616e to
90b635b
Compare
CI should check that C++ and Rust code can communicate via mw::com. To simplify the tests the CLI interface of the Rust code has been more aligned with the C++ interface.
Fixes #38