We classified this failure as flaky rather than a code change because the failing test (shared widget CSS stays applied when navigating from lazy to static route) lives in a project untouched by this PR and concerns CSS chunk persistence during client-side navigation — unrelated to the SSR link-prop optimizations introduced here. The task carries a 4.74% historical flakiness rate, and the empty computed style is consistent with a known timing race between CSS chunk injection and style evaluation in E2E tests.
Failed after FFloView latest
Merge branch 'main' into codex/solid-link-server-all
83166aab9b4Open on GitHubSelf-Healing CI
Classification: Flaky task
An empty commit was automatically applied to the branch to trigger a new CI pipeline execution to resolve the flaky task.
The failing task is tanstack-solid-start-e2e-start-manifest:test:e2e, which belongs to a project not listed in the PR's touched projects (["root", "@tanstack/solid-router"]).
The PR changes are confined to packages/solid-router/src/link.tsx — specifically restructuring how server-rendered links skip hydration, preload, intersection-observer setup, and event-handler wiring. This is an SSR optimization for link rendering.
The failing test ("shared widget CSS stays applied when navigating from lazy to static route") checks that SharedWidget-BAtMnCRs.css border color (rgb(249, 115, 22)) remains applied after a client-side navigation from a lazy-loaded route to a static route. This is about CSS chunk persistence in the start manifest system — entirely unrelated to SSR link prop computation.
The task has a recorded flakiness rate of 4.74%, confirming it has failed intermittently on unchanged code before. The empty computed style received during the assertion is consistent with a timing race between CSS chunk injection and the test's style evaluation — a well-known pattern in E2E CSS persistence tests.
No matching failure was found in the comparison branch (8328), ruling out a shared environment regression introduced across branches.