We determined this failure is unrelated to the PR's changes, which only add a cache-bust key and a sandboxing config. The test "shared widget CSS stays applied when navigating from lazy to static route" has a known flakiness rate of ~12%, indicating a Playwright timing issue where CSS is not yet applied at assertion time. A rerun should resolve this.
Failed after NBNicolas BeaussartView latest
Merge branch 'main' into test-sandboxing
75923960ee2Open 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 test "shared widget CSS stays applied when navigating from lazy to static route" expects a CSS border color of rgb(249, 115, 22) but receives an empty string — a classic symptom of a Playwright rendering/timing race condition where the CSS has not yet been applied at the time of assertion.
The PR changes are limited to:
- Adding a
bust-cachkey innx.jsonto force cache invalidation - Adding
.nx/workflows/sandboxing-config.yamlto exclude.npmrcfrom sandbox reads
Neither of these changes touches any routing logic, CSS, or component code related to the failing test.
The task has a historical flakiness rate of 11.8%, confirming it fails intermittently without any code change triggering it.
No similar failures were found in branch 7926, ruling out a pre-existing environmental regression.
Given that the PR changes are entirely infrastructure/cache-related and cannot logically affect CSS application during client-side navigation, and that the task is known to be non-deterministic, this is classified as a flaky test that can be resolved with a rerun.