ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Total Tests: 35 Suites 📂: 0 Passed ✅: 35 Failed ❌: 0 Canceled 🚫: 0 Skipped ⏭️: 0 Todo 📝: 0 Duration 🕐: 653.122ms

Total Tests: 4455 Suites 📂: 0 Passed ✅: 4433 Failed ❌: 0 Canceled 🚫: 0 Skipped ⏭️: 3 Todo 📝: 19 Duration 🕐: 47771.908ms

Total Tests: 4455 Suites 📂: 0 Passed ✅: 4433 Failed ❌: 0 Canceled 🚫: 0 Skipped ⏭️: 3 Todo 📝: 19 Duration 🕐: 49925.012ms

Total Tests: 4457 Suites 📂: 0 Passed ✅: 4438 Failed ❌: 0 Canceled 🚫: 0 Skipped ⏭️: 0 Todo 📝: 19 Duration 🕐: 51994.649ms

Total Tests: 1 Suites 📂: 0 Passed ✅: 1 Failed ❌: 0 Canceled 🚫: 0 Skipped ⏭️: 0 Todo 📝: 0 Duration 🕐: 388.021ms

If a New Relic agent started a trace, and then a non-New Relic tracer propagated the trace, then the traceparent span ID would updated by the non-New Relic tracer, but not the span ID in the New Relic tracestate entry

If the parent is a New Relic agent with span events disabled it SHOULD omit span id from the tracestate. This verifies agents propagate Trace Context payloads when the parent is a New Relic agent with span events disabled

the transaction must be marked sampled=true so a Span event is created

beware the casing!

If the new relic payload's version is higher than 0, with extra new fields, all the existing fields should be read and used, and the extra future fields should be ignored.

outbound newrelic headers are built from w3c headers, ignoring inbound newrelic headers

If the traceparent header is present on an inbound request, conforming agents MUST ignore any newrelic header. If the traceparent header is invalid, a new trace MUST be started. The newrelic header MUST be used _only_ when traceparent is _missing_.

Tests correct handling of newrelic headers Agents may receive a traceId in upper-case, or shorter than 32 characters. In this case, the traceId MUST be left-padded with zeros AND lower-cased The outbound newrelic header, if configured, should include the traceId as-received.

With both spans and transaction events disabled, there will be no events to verify intrinsics against. tracestate.span_id and tracestate.transaction_id are not expected on outbound payloads.

Test a payload that originates from a serverless agent. The only difference in the payload between a serverless and non-serverless agent is the `appId` in the tracestate header will be 'Unknown'.

Total Tests: 1 Suites 📂: 0 Passed ✅: 1 Failed ❌: 0 Canceled 🚫: 0 Skipped ⏭️: 0 Todo 📝: 0 Duration 🕐: 446.321ms

If a New Relic agent started a trace, and then a non-New Relic tracer propagated the trace, then the traceparent span ID would updated by the non-New Relic tracer, but not the span ID in the New Relic tracestate entry

If the parent is a New Relic agent with span events disabled it SHOULD omit span id from the tracestate. This verifies agents propagate Trace Context payloads when the parent is a New Relic agent with span events disabled

the transaction must be marked sampled=true so a Span event is created

beware the casing!

If the new relic payload's version is higher than 0, with extra new fields, all the existing fields should be read and used, and the extra future fields should be ignored.

outbound newrelic headers are built from w3c headers, ignoring inbound newrelic headers

If the traceparent header is present on an inbound request, conforming agents MUST ignore any newrelic header. If the traceparent header is invalid, a new trace MUST be started. The newrelic header MUST be used _only_ when traceparent is _missing_.

Tests correct handling of newrelic headers Agents may receive a traceId in upper-case, or shorter than 32 characters. In this case, the traceId MUST be left-padded with zeros AND lower-cased The outbound newrelic header, if configured, should include the traceId as-received.

With both spans and transaction events disabled, there will be no events to verify intrinsics against. tracestate.span_id and tracestate.transaction_id are not expected on outbound payloads.

Test a payload that originates from a serverless agent. The only difference in the payload between a serverless and non-serverless agent is the `appId` in the tracestate header will be 'Unknown'.

Total Tests: 1 Suites 📂: 0 Passed ✅: 1 Failed ❌: 0 Canceled 🚫: 0 Skipped ⏭️: 0 Todo 📝: 0 Duration 🕐: 398.276ms

If a New Relic agent started a trace, and then a non-New Relic tracer propagated the trace, then the traceparent span ID would updated by the non-New Relic tracer, but not the span ID in the New Relic tracestate entry

If the parent is a New Relic agent with span events disabled it SHOULD omit span id from the tracestate. This verifies agents propagate Trace Context payloads when the parent is a New Relic agent with span events disabled

the transaction must be marked sampled=true so a Span event is created

beware the casing!

If the new relic payload's version is higher than 0, with extra new fields, all the existing fields should be read and used, and the extra future fields should be ignored.

outbound newrelic headers are built from w3c headers, ignoring inbound newrelic headers

If the traceparent header is present on an inbound request, conforming agents MUST ignore any newrelic header. If the traceparent header is invalid, a new trace MUST be started. The newrelic header MUST be used _only_ when traceparent is _missing_.

Tests correct handling of newrelic headers Agents may receive a traceId in upper-case, or shorter than 32 characters. In this case, the traceId MUST be left-padded with zeros AND lower-cased The outbound newrelic header, if configured, should include the traceId as-received.

With both spans and transaction events disabled, there will be no events to verify intrinsics against. tracestate.span_id and tracestate.transaction_id are not expected on outbound payloads.