2024-02-23
emulator.wtf web app
- Improved the performance of displaying and paging test runs in the web app
The test run result links now contain a few details about the run:
ew-cli. We now retry failed requests in a more robust way, and we also increased
some of the longer network call timeouts (like file uploads). This should help in cases where you are running many tests
in parallel from the same CI job.ew-cli to 0.10.9ew-cli to 0.10.9setup-ew-cli to v0.9.9model=Tablet10 would capture corrupted video
due to mismatched encoder parameters.--test-target and
it expanded to multiple parametric test cases. This was previously causing the test run to fail
and works now without issue.Atlantic/Reykjavik timezone (same as UTC).
This should improve compatibility with tests that use the system timezone identifier
and don’t support the Etc/UTC timezone identifier.surfaceflinger process and the whole System UI with it,
we’ll trigger an automatic retry of the test run. This is a rare event that may happen with
tests making heavy use of surfaces like utilizing the camera preview. The retry does not add any
billable minutes to your account. NOTE: just like with flaky repeats, we do not attempt any retries
when using the side-effects flag.org.json library to a newer version.emulator-wtf/invoke@v0.9.7 and emulator-wtf/setup-ew-cli@v0.9.8 to use the node20 GitHub Actions runtime.ew-cli to 0.10.7useTestStorageService flag would run all the tests again in
every shard. NOTE: there is a known issue about AndroidJUnitRunner 1.5.2 or earlier, we will now
warn you if you happen to have this combination.--test-targets would not work as expected when used together with balanced sharding.ew-cli fails fast when trying to run tests on an apk containing only ARM binaries - our emulators are x86/x86_64.ew-cli output.gpu=auto flag
(e.g. --device model=Pixel2,version=34,gpu=auto) to enable GPU acceleration. Read our blog post on
the benefits of GPU acceleration here.--json flag or the summary output format, the consumed test run minutes are now available in the JSON outputs of test runs. The consumed test run minutes are available under the billableMinutes key in the JSON output.
This is useful when estimating the cost of using emulator.wtf in the long-term. Read more on how
we calculate billableMinutes here.0.10.0 binary due to minification issues in 0.10.1.device=Pixel2Atd,version=31device=Pixel2Atd,version=32device=Pixel2Atd,version=33device=Pixel7Atd,version=31device=Pixel7Atd,version=32device=Pixel7Atd,version=33device=Tablet10Atd,version=31device=Tablet10Atd,version=32device=Tablet10Atd,version=33device=NexusLowResAtd,version=31device=NexusLowResAtd,version=32device=NexusLowResAtd,version=33