Thanks to m4 expansion I had to change it in tests/system-dpdk-testsuite for retesting.
The real fix would be in ./tests/system-dpdk-macros.at though.
Adding the following to the rules made it work:
/TELEMETRY: Socket write base info to client failed/d
Now the questions is "is this a warning that is fine to have in the tests or is this masking a legit error?"
I'll propose that to openswitch setting a set of people on CC that deal with those topics.
In that discussion we can hopefully conclude the above question.
P.S.That was a long strange trip - I wish the test would say something more clear like "I found this .... in the log which I didn't expect", but since it does not (clear enough to me at least) that was a debugging rabbit hole.
Thanks to m4 expansion I had to change it in tests/system- dpdk-testsuite for retesting. system- dpdk-macros. at though.
The real fix would be in ./tests/
Adding the following to the rules made it work:
/TELEMETRY: Socket write base info to client failed/d
Now the questions is "is this a warning that is fine to have in the tests or is this masking a legit error?"
I'll propose that to openswitch setting a set of people on CC that deal with those topics.
In that discussion we can hopefully conclude the above question.
P.S.That was a long strange trip - I wish the test would say something more clear like "I found this .... in the log which I didn't expect", but since it does not (clear enough to me at least) that was a debugging rabbit hole.