Skip to content

browser-integration-tests: drop static pins from non-tracing suites #24145

Description

@andreiborza

Follow the porting recipe in the parent issue.

Largest group by file count and the smallest by effort. Around 226 pinned init.js files never assert on a transaction envelope, so the pin just needs to go.

Suites (pin removal only)

  • replay/* (78 files, the single biggest block)
  • feedback/*, sessions/*, errors/*, stacktraces/*, transport/*, wasm/*, old-sdk-interop/*, manual-client/*, ipv6
  • public-api/* except the span surface dirs owned by the trace semantics sub-issue
  • integrations/* except httpclient, which the trace semantics sub-issue owns

Watch-outs

  • replay/dsc and public-api/dataCollection do assert on the trace context, so they need a rewrite rather than a pin removal.
  • profiling/traceLifecycleMode_multiple-chunks and traceLifecycleMode_overlapping-spans intentionally test the static lifecycle. Leave their pins in place.
  • integrations/cultureContext-streamed and integrations/httpContext-streamed are twins. Fold them back into their static originals.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

TaskjavascriptPull requests that update javascript code

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions