We identified the failure in tanstack-react-start-e2e-rsc:test:e2e--rsbuild-ssr--shard-4-of-6 as an environment state issue: the Playwright external test server could not bind to port 32795 (EADDRINUSE), indicating another process was already occupying that port at the time of the run. Our analysis confirmed no connection to this PR's router core changes, and no similar failures were found in other branches, pointing to a transient CI infrastructure condition that should resolve on a rerun.
don't fail nav on lifecycle user error
78051c28ed7Open on GitHubSelf-Healing CI
An empty commit was applied to the branch to trigger a new CI pipeline execution to resolve the environment issue.
The failing task tanstack-react-start-e2e-rsc:test:e2e--rsbuild-ssr--shard-4-of-6 produced an EADDRINUSE error on port 32795, meaning another process was already bound to that port when the Playwright external test server tried to start.
This was not classified as a code change for the following reasons:
No logical connection to the PR changes: The PR is a router core lane/match/loader rewrite focused on routing lifecycle, SSR loading, and navigation transitions. None of those changes involve network port allocation or test server configuration.
Flakiness rate is 0%: This rules out a recurring flaky test, but the port conflict is still a runtime infrastructure condition — not a deterministic failure caused by the diff.
No similar failures in other branches: The similar-task-failure-detector found no matching failures in other branches, which could suggest a transient environment condition specific to the CI machine at the time this run executed.
Port conflicts are environment artifacts: An
EADDRINUSEerror on localhost indicates a pre-existing or concurrent process occupying port 32795. This is an environment state condition (e.g., a leftover process from a prior test shard or a concurrent shard binding to the same port) and is not something the PR's code changes could have introduced.