During the last contrib release, there were a few flaky tests that cause some problems.

https://develocity.opentelemetry.io/s/kzarodjoam5t6/tests/task/:inferred-spans:test/details/io.opentelemetry.contrib.inferredspans.InferredSpansTest/testSetProfilerInterval()?top-execution=1

Same basic thing with the SamplingProfilerTest.

Seems like maybe the profiler isn't being reset correctly between tests or there is some other unexpected test interaction.