Ignacy Łątka 41a8ed83aa test(e2e): hold simulator-server to the resize the retry scale rests on ...

REFUSED_CAPTURE_RETRY_SCALE recovers the frame rather than a reduced one only
because the server rounds `dimension x scale` back to the dimension. The binary
is not in-tree (scripts/download-simulator-server.sh fetches a rolling tag), so
the unit suite models that contract instead of pinning it: a build that
truncated, or that widened its own below-1 gate past 1e-6, would flip every
Android snapshot key or send the retry back into the refusing path, with the
suite still green.

drive-device.sh captures unscaled and at the constant's own value and compares
dimensions, reading the scale out of simulator-client.ts so the check follows
the constant rather than restating it. Enabled on the iOS simulator job, the
only one here on a simulator-server backend - a scale below 1 on Chromium goes
through the optional sharp dependency instead. e2e-device-smoke already
triggers on simulator-client.ts, so the file that owns the constant runs it.

Verified on an iPhone simulator through a real tool-server: unscaled and
0.999999 both return 1320x2868, and the two files are byte-identical. Against a
stub server that truncates, the check fails naming both dimensions; with the
constant mutated to 0.3 it fails at 324x727; with the constant renamed it
hard-fails rather than silently passing.

2026-09-02 20:16:28 +02:00

..

drive-device.sh

test(e2e): hold simulator-server to the resize the retry scale rests on

2026-09-02 20:16:28 +02:00