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
Currently latency tests are using code (publisher and subscriber source code) coming from private repositories.
The workaround to use them is to build from these source docker images and put them in belonging directory src/trafgen and src/svtools.
The problem is that latency tests can not be executed by person who does not have access to these sources.
The solution would be to set svtools (subscriber source code) and trafgen (publisher source code) repositories as public.
The text was updated successfully, but these errors were encountered:
Currently latency tests are using code (publisher and subscriber source code) coming from private repositories.
The workaround to use them is to build from these source docker images and put them in belonging directory
src/trafgen
andsrc/svtools
.The problem is that latency tests can not be executed by person who does not have access to these sources.
The solution would be to set svtools (subscriber source code) and trafgen (publisher source code) repositories as public.
The text was updated successfully, but these errors were encountered: