feat(node): Wire up SentryTracerProvider #49538
Annotations
2 errors and 1 notice
|
Run E2E test
Process completed with exit code 1.
|
|
Run E2E test:
../../_temp/test-application/tests/server-components.test.ts#L118
1) [chromium] › tests/server-components.test.ts:99:5 › Should capture an error and transaction for a app router page
Error: expect(received).toContainEqual(expected) // deep equality
Expected value: ObjectContaining {"description": "render route (app) /server-component/faulty", "status": "internal_error"}
Received array: [{"data": {"next.route": "/server-component/faulty", "next.span_name": "render route (app) /server-component/faulty", "next.span_type": "AppRender.getBodyResult", "sentry.origin": "auto"}, "description": "render route (app) /server-component/faulty", "origin": "auto", "parent_span_id": "a7e6134016bd08e2", "span_id": "a97f69e9deb257d9", "start_timestamp": 1782431804.0625565, "status": "An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.", "timestamp": 1782431804.0773644, "trace_id": "d87b729f0d9a4820990c4bed4682232d"}]
116 | // Transaction should have status ok, because the http status is ok, but the render component span should be internal_error
117 | expect(transactionEvent.contexts?.trace?.status).toBe('ok');
> 118 | expect(transactionEvent.spans).toContainEqual(
| ^
119 | expect.objectContaining({
120 | description: 'render route (app) /server-component/faulty',
121 | status: 'internal_error',
at /home/runner/work/_temp/test-application/tests/server-components.test.ts:118:34
|
|
Run E2E test
1 failed
[chromium] › tests/server-components.test.ts:99:5 › Should capture an error and transaction for a app router page
6 skipped
27 passed (1.1m)
|
background
wait
wait-all
cancel
parallel
Loading