getsentry / getsentry/sentry-javascript
[Flaky CI]: E2E nextjs-16-streaming Test - [chromium] › tests/pageload-tracing.test.ts:4:5 › Server and client pageload spans should share the same trace
Open
Flaky Test
Next.js
Tests
- Dominant language
- TypeScript
- Stars
- 8.7k
- Forks
- 1.8k
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 515
Description
### Flakiness Type
Other / Unknown
### Name of Job
E2E nextjs-16-streaming Test
### Name of Test
[chromium] › tests/pageload-tracing.test.ts:4:5 › Server and client pageload spans should share the same trace
### Link to Test Run
https://github.com/getsentry/sentry-javascript/actions/runs/28595282073/job/84791210739
---
_This issue was automatically created._
Contributor guide
Research direction
Start with tests/pageload-tracing.test.ts:4:5 and the linked GitHub Actions run for E2E nextjs-16-streaming. Reproduce the Chromium failure and inspect the server/client pageload trace assertions; done means the test reliably verifies shared traces without intermittent failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, typescript
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100