You can see in our hapi E2E tests that there are a bunch of span warnings from OTEL:
[WebServer] Sentry Logger [warn]: Can not execute the operation on ended Span {traceId: bb29cf03126538cae9ee1281c664947b, spanId: f6f31230cc25d105}
[WebServer] Sentry Logger [warn]: Can not execute the operation on ended Span {traceId: bb29cf0312[65](https://github.com/getsentry/sentry-javascript/actions/runs/9269480097/job/25500625012#step:12:66)38cae9ee1281c664947b, spanId: f6f31230cc25d105}
Sentry Logger [warn]: Can not execute the operation on ended Span {traceId: bb29cf03126538cae9ee1281c[66](https://github.com/getsentry/sentry-javascript/actions/runs/9269480097/job/25500625012#step:12:67)4947b, spanId: f6f31230cc25d105}
Sentry Logger [warn]: Can not execute the operation on ended Span {traceId: bb29cf03126538cae9ee1281c664947b, spanId: f6f31230cc25d105}
Sentry Logger [warn]: Can not execute the operation on ended Span {traceId: bb29cf03126538cae9ee1281c664947b, spanId: f6f31230cc25d105}
Sentry Logger [warn]: Can not execute the operation on ended Span {traceId: bb29cf03126538cae9ee1281c664947b, spanId: f6f31230cc25d105}
Sentry Logger [warn]: Can not execute the operation on ended Span {traceId: bb29cf03126538cae9ee1281c664947b, spanId: f6f31230cc25d105}
Sentry Logger [warn]: Can not execute the operation on ended Span {traceId: bb29cf03126538cae9ee1281c664947b, spanId: f6f31230cc25d105}
Sentry Logger [warn]: Can not execute the operation on ended Span {traceId: bb29cf03126538cae9ee1281c664947b, spanId: f6f31230cc25d105}
[WebServer] Sentry Logger [warn]: Can not execute the operation on ended Span {traceId: bb29cf03126538cae9ee1281c664947b, spanId: f6f31230cc25d105}
Error: Sentry Logger [error]: GET bb29cf03126538cae9ee1281c664947b-f6f31230cc25d105 - You can only call end() on a span once.
We should investigate and possibly fix this. (I could also see this when running the test locally)
You can see in our hapi E2E tests that there are a bunch of span warnings from OTEL:
https://github.com/getsentry/sentry-javascript/actions/runs/9269480097/job/25500625012#step:12:65
We should investigate and possibly fix this. (I could also see this when running the test locally)