This PR fixes #108, for which there is already another PR #116 (from @VladoLavor) that was aiming to resolve the random failures, but since it also contains a large code refactor for entire trace functionality, we decided to do a fix for random failures first, so make it for v0.8.0 and then deal with the trace refactor separately in the next release.
This PR skps the existing unit tests that had random failures and adds new integration tests which test trace functionality against real VPP instance. This is because the suspected reason for random failures is probably some race condition cause by request/reply handling in mock adapter.
This PR fixes #108, for which there is already another PR #116 (from @VladoLavor) that was aiming to resolve the random failures, but since it also contains a large code refactor for entire trace functionality, we decided to do a fix for random failures first, so make it for v0.8.0 and then deal with the trace refactor separately in the next release.
This PR skps the existing unit tests that had random failures and adds new integration tests which test trace functionality against real VPP instance. This is because the suspected reason for random failures is probably some race condition cause by request/reply handling in mock adapter.
Summary of changes: