You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: