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, for tracing test, we have code that checks if tracing is used as a part of CNF installation, and writes info about it to the config. During the test - config is read and result is given based on written info.
Problem is that adding complexity to the CNF setup process is not ideal (#2036), and from my point of view - we should find another way to check if Jaeger tracing is enabled in CNF.
Also, the tests seems a bit too specific as it is tied to using Jaeger. Maybe some other way could be found.
The text was updated successfully, but these errors were encountered:
Currently, for tracing test, we have code that checks if tracing is used as a part of CNF installation, and writes info about it to the config. During the test - config is read and result is given based on written info.
Problem is that adding complexity to the CNF setup process is not ideal (#2036), and from my point of view - we should find another way to check if Jaeger tracing is enabled in CNF.
Also, the tests seems a bit too specific as it is tied to using Jaeger. Maybe some other way could be found.
The text was updated successfully, but these errors were encountered: