router
Failed after Aautofix-ci[bot]

ci: apply automated fixes (attempt 2/3)

75907634019Open on GitHub

Self-Healing CI

Classification: Flaky task

We classified this failure as a flaky test rather than a code change because the tanstack-solid-start-e2e-start-manifest project was not touched by this PR, and the failure is unrelated to the Rsbuild SSR asset URL fix it introduces. The test has a ~11% historical flakiness rate, and the empty borderTopColor assertion after client-side navigation is a known timing/race condition in this fixture — a rerun should resolve it.

An empty commit was automatically applied to the branch to trigger a new CI pipeline execution to resolve the flaky task.

The failure was classified as flaky_task rather than code_change for the following reasons:

  1. The failing project is not in touched_projects. The tanstack-solid-start-e2e-start-manifest project was not modified by this PR. The touched_projects list is empty ([]), meaning no direct relationship exists between the PR's changes and the failing test's project.

  2. The PR's changes are unrelated to the failing test's scope. This PR focuses on aligning Rsbuild SSR asset URLs for css?url imports. The failing test lives in a Vite-based start-manifest fixture — a completely different build system and test area.

  3. The error is consistent with a timing/race condition. The test asserts getComputedStyle(element).borderTopColor equals rgb(249, 115, 22) after client-side navigation from a lazy to a static route. Receiving an empty string instead is a well-known symptom of CSS not yet being computed at assertion time — not a sign of broken logic introduced by a code change.

  4. Confirmed flakiness history. The task has a measured flakiness rate of ~10.96%, meaning it has a documented history of intermittent failures independent of any code changes. This strongly supports a flaky_task classification rather than code_change.