You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Root cause note: the test asserted a hard `maxLatency <= 120ms` on the single slowest MutationObserver sample, which was sensitive to one-off runner scheduling spikes in the release workflow even when the same Linux browser suite passed in `PR Validation`.
236
236
- Intended fix path: keep the strong no-visible-input/no-long-task checks, but evaluate typing responsiveness with a bounded spike plus a stable `p95` latency threshold instead of a single-sample maximum.
237
+
- GitHub run `23817217598` confirmed a workflow-level difference still remained after the typing-probe stabilization:
238
+
-`PR Validation` run `23817221509` passed on the same commit while the release workflow still failed in `Build And Test`.
239
+
- Root cause note: the release workflow exported Pages and release publishing variables globally, so the validation job did not actually run under the same environment contract as `PR Validation`.
240
+
- Intended fix path: scope release-only environment variables to the release-preparation and publish jobs, leaving the release validation job with the same build/test environment as `PR Validation`.
237
241
- Local validation after the browser-suite stability fixes passed:
0 commit comments