Skip to content

feat: Add strict trace continuation support #13709

feat: Add strict trace continuation support

feat: Add strict trace continuation support #13709

Triggered via pull request March 30, 2026 12:22
Status Failure
Total duration 16m 17s
Artifacts 1

build.yml

on: pull_request
Build Job ubuntu-latest - Java 17
16m 12s
Build Job ubuntu-latest - Java 17
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 2 warnings
io.sentry.opentelemetry.SentrySpanProcessorTest ► propagator can extract and result is used for transaction and attached on inject: sentry-opentelemetry/sentry-opentelemetry-core/build/test-results/test/TEST-io.sentry.opentelemetry.SentrySpanProcessorTest.xml#L0
Failed test found in: sentry-opentelemetry/sentry-opentelemetry-core/build/test-results/test/TEST-io.sentry.opentelemetry.SentrySpanProcessorTest.xml Error: org.junit.ComparisonFailure: org.junit.ComparisonFailure: expected:<[2722d9f6ec019ade60c776169d9a8904]> but was:<[f10fd9936ce517743de337c7a3b68987]>
io.sentry.opentelemetry.SentrySpanProcessorTest ► links error to OTEL transaction: sentry-opentelemetry/sentry-opentelemetry-core/build/test-results/test/TEST-io.sentry.opentelemetry.SentrySpanProcessorTest.xml#L0
Failed test found in: sentry-opentelemetry/sentry-opentelemetry-core/build/test-results/test/TEST-io.sentry.opentelemetry.SentrySpanProcessorTest.xml Error: org.mockito.exceptions.verification.junit.ArgumentsAreDifferent: Argument(s) are different! Wanted: iScopes.startTransaction( <custom argument matcher>, <custom argument matcher> ); -> at io.sentry.opentelemetry.SentrySpanProcessorTest.thenTransactionIsStarted(SentrySpanProcessorTest.kt:422) Actual invocations have different arguments: iScopes.isEnabled( ); -> at io.sentry.opentelemetry.SentrySpanProcessor.hasSentryBeenInitialized(SentrySpanProcessor.java:365) iScopes.getOptions( ); -> at io.sentry.opentelemetry.SentrySpanProcessor.ensurePrerequisites(SentrySpanProcessor.java:235) iScopes.getOptions( ); -> at io.sentry.opentelemetry.SentrySpanProcessor.onStart(SentrySpanProcessor.java:112) iScopes.startTransaction( io.sentry.TransactionContext@411bd3d2, io.sentry.TransactionOptions@4fbe486c ); -> at io.sentry.opentelemetry.SentrySpanProcessor.onStart(SentrySpanProcessor.java:145)
io.sentry.opentelemetry.SentrySpanProcessorTest ► sentry-trace without baggage continues trace: sentry-opentelemetry/sentry-opentelemetry-core/build/test-results/test/TEST-io.sentry.opentelemetry.SentrySpanProcessorTest.xml#L0
Failed test found in: sentry-opentelemetry/sentry-opentelemetry-core/build/test-results/test/TEST-io.sentry.opentelemetry.SentrySpanProcessorTest.xml Error: org.junit.ComparisonFailure: org.junit.ComparisonFailure: expected:<[2722d9f6ec019ade60c776169d9a8904]> but was:<[fb5b781370365f2cb1b2bcaa80a56f5c]>
Build Job ubuntu-latest - Java 17
Process completed with exit code 2.
Build Job ubuntu-latest - Java 17
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: phoenix-actions/test-reporting@f957cd93fc2d848d556fa0d03c57bc79127b6b5e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build Job ubuntu-latest - Java 17
Test report summary exceeded limit of 65535 bytes and will be trimmed

Artifacts

Produced during runtime
Name Size Digest
test-results-build
2.05 MB
sha256:2baa62bd8cc8392d316a85582f8ee5e9f732ceca6e98eeb95681b9de62ae2d77