Failed
Open on GitHub

fix(router): process queued viewport transitions in order

SSheraff
71a0e13c
8044Latest execution

Self-Healing CI

Classification: Environment state

We classified this failure as an environment issue rather than a code change. The e2e test failed because port 41763 was already in use (EADDRINUSE) when the external preview server tried to start — a transient infrastructure conflict unrelated to our PR changes. None of the modified projects touch the failing e2e project, and no port or test configuration was altered in this PR.

An empty commit was applied to the branch to trigger a new CI pipeline execution to resolve the environment issue.

The failing task tanstack-router-e2e-vue-basic-file-sfc:test:e2e was not classified as a code change for the following reasons:

  1. Port conflict error, not a logic error The task failed with EADDRINUSE: address already in use 127.0.0.1:41763 — this is an infrastructure-level failure where another process had already bound to port 41763 before the test server could start.

  2. Project not touched by the PR The PR modifies @tanstack/react-router, @tanstack/router-core, @tanstack/solid-router, @tanstack/vue-router, and root. The failing project tanstack-router-e2e-vue-basic-file-sfc is not in this list, meaning none of the PR's changes directly affect it.

  3. No e2e or port configuration changes in the diff Reviewing the PR diff, there are no modifications to e2e test files, Playwright configuration, Vite preview settings, or any port assignments. The PR is purely focused on preload delay logic in link components and related unit tests.

  4. Flakiness rate is 0% A flakiness rate of 0% rules out this being a known intermittent/flaky test failure. The failure is deterministic given the environment state.

  5. Conclusion All evidence points to a transient environment issue — port 41763 was occupied by a leftover process from a prior run or a concurrent job. The PR code had no causal relationship to this failure.