Skip to content

4.1.7: Avoid cross-test config contamination in microprofile/telemetry tests #9758

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 7, 2025
Merged

4.1.7: Avoid cross-test config contamination in microprofile/telemetry tests #9758

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions microprofile/telemetry/pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -147,7 +147,26 @@
<configuration>
<systemPropertyVariables>
<otel.bsp.schedule.delay>${otel.bsp.schedule.delay}</otel.bsp.schedule.delay>
<otel.sdk.disabled>false</otel.sdk.disabled>
</systemPropertyVariables>
<excludes>
<exclude>**/AgentDetectorTest.java</exclude>
</excludes>
</configuration>
</execution>
<execution>
<!--
This test does not need an active OTel SDK so run it separately to prevent it from running first
and leaving other tests with a no-op Otel which will cause them to fail.
-->
<id>agent-detector-tests</id>
<goals>
<goal>test</goal>
</goals>
<configuration>
<includes>
<include>**/AgentDetectorTest.java</include>
</includes>
</configuration>
</execution>
</executions>
Expand Down
Loading