fix(web): restore the Feature Toggles restart action (#2236)
Co-authored-by: Carlos Florencio <carlosmflorencio@gmail.com>
This commit is contained in:
@@ -145,12 +145,12 @@ Start by matching CI as closely as possible, then add pressure deliberately:
|
||||
full spec file or full shard with the same resource limits before declaring
|
||||
a flake non-reproducible.
|
||||
|
||||
A test that passes only after a Playwright retry is still a failure signal.
|
||||
During triage disable per-spec retry overrides and use `--retries=0`. When
|
||||
isolated repeats pass but the same shard position fails, binary-search the
|
||||
preceding spec files under one worker until the smallest ordered sequence
|
||||
reproduces the shared-state leak; the fix is complete only when that sequence
|
||||
passes with retries disabled.
|
||||
The config uses `failOnFlakyTests: !CI`: local runs fail on a flaky retry, while
|
||||
CI temporarily tolerates one. Either result is a failure signal for agents:
|
||||
reproduce it locally with per-spec overrides disabled and `--retries=0`; never
|
||||
rerun until it happens to pass. If isolated repeats stay green but the shard
|
||||
fails, binary-search preceding specs in one worker. The fix is complete only
|
||||
when the smallest reproducing sequence passes without retries.
|
||||
|
||||
Record the exact command, resource limits, repeat number, and failure artifact
|
||||
path. Always inspect `error-context.md`; mobile/terminal flakes often show
|
||||
|
||||
Reference in New Issue
Block a user