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

Allow testing of dynamic linking of OV libraries in CI #62

Open
mhthies opened this issue Aug 24, 2021 · 0 comments
Open

Allow testing of dynamic linking of OV libraries in CI #62

mhthies opened this issue Aug 24, 2021 · 0 comments

Comments

@mhthies
Copy link
Collaborator

mhthies commented Aug 24, 2021

Due to the dynamic linking of OV libraries, most linker errors (missing symbols from other libraries) only occur at runtime, more precisely, when loading the library in the ov_runtimeserver. Thus, it would be useful to cover this stage in continous integration.

On Linux, the test could be performed quite easily by starting ov_runtimeserver with the timeout command and pass all libraries to be tested via the -w cli option. However, currently a failure in loading a library cannot easily be detected, since ov_runtimeserver only logs the failure but keeps on running normally. For this test to work, we would need to add a "exit on library loading failure" command line option, which would instruct ov_runtimeserver to exit with a non-zero exit code when loading a library fails.

For Windows CI, I don't know if there is something similar to the timeout command in PowerShell.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant