We classified this failure as an environment issue rather than a code change. The test failed with EADDRINUSE on port 32915, meaning another process had already claimed that port before the test's external server could start — unrelated to the PR's internal key renames in @tanstack/start-client-core. No port configuration or test infrastructure was modified by this PR.
Self-Healing CI
Classification: Environment state
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-2-of-6 was not classified as a code change for the following reasons:
Project not touched by the PR: The PR only modifies
rootand@tanstack/start-client-core. The failing projecttanstack-react-start-e2e-rscwas not affected by any of the PR's file changes.Error is a port conflict, not a logic failure: The test failed with
EADDRINUSE: address already in use 127.0.0.1:32915. This means port 32915 was already occupied by another process when the test's "external" web server tried to start. This is an infrastructure/environment issue, not a symptom of broken application code.No port configuration was changed in the PR: The PR renames internal result keys (
getOrCreateStream→getStream,jsonChunks→chunks) within the frame decoder. No port assignments, server configuration, or test infrastructure was modified.Flakiness rate is 0%: A rate of 0% rules out classification as a flaky task, leaving environment_state as the only remaining category.
No similar failures in branch 7976: The similar-task-failure check returned no matches, confirming this is not a recurring regression introduced across branches.