4.1.7: Avoid cross-test config contamination in microprofile/telemetry tests
#9758
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ts (helidon-io#9685) * Avoid cross-test config contamination * Remove exclusion of test from Windows
barchetta
added
the
backport
oracle-contributor-agreement
bot
added
the
OCA Verified
tjquinno
approved these changes
Feb 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport #9685 to Helidon 4.1.7
Description
Resolves #9513
Intermittent test failures in
micrometer/telemetryseem to be due to tests which need a full-featured OTel instance inheriting a default no-op one from other tests which run earlier which do not need a full OTel and in fact establish a no-op default one.This PR segregates the test that does not enforce an active OTel from the others.
Documentation
No impact.