GlobalTracer breaks tests because it can be initialized only once

GlobalTracer.register throws an exception when called again with another tracer instance. It makes unit tests fail if they happen to initialize GlobalTracer.

Has anyone run into this problem? I could run tests in separate JVM instances, but I’d rather not. Maybe adding a “reset” method would make it easier to use for testing purposes?

[yurishkuro]

I always like making exceptions more helpful to the users. If this is a common scenario in tests, we should probably extend the exception message to say “if you are getting this exception when running unit tests, see {url}” and link to the doc explaining how tests should be written.

[pavolloffay]

I think we should rather provide reset method directly on the GlobalTracer. It will make things much simpler, consumers should understand implications when calling it.