ci: retry flaky iOS tests and run Android emulator headless

[harrshita123]

Part of #255

iOS was failing due to the simulator debug connection timing out, so wrapped the test step with nick-fields/retry (2 attempts).

For Android added the headless emulator flags (-no-window -gpu swiftshader_indirect -no audio -no-boot-anim).

[HamdaanAliQuatil]

@harrshita123 the new dart2wasm smoke job is the right direction. It is failing because two existing tests still expect the old dart2wasm error string, JavaScriptError.

In the current toolchain, Chrome/Dart2Wasm surfaces the browser DOMException name instead: QuotaExceededError for oversized buffers and TypeMismatchError for non-integer typed arrays. Could you update those two expectations to accept both forms?

[harrshita123]

@harrshita123 the new dart2wasm smoke job is the right direction. It is failing because two existing tests still expect the old dart2wasm error string, JavaScriptError.

In the current toolchain, Chrome/Dart2Wasm surfaces the browser DOMException name instead: QuotaExceededError for oversized buffers and TypeMismatchError for non-integer typed arrays. Could you update those two expectations to accept both forms?

Updated this. I changed the two getRandomValues expectations so they accept both the older JavaScriptError form and the newer DOMException-name form surfaced by the current dart2wasm toolchain.

[HamdaanAliQuatil]

The remaining timeouts are now coming from the chromedriver flutter drive -d chrome integration step. On Linux, the test prints All tests passed! and then hangs during teardown. On Windows, DWDS fails to establish the Chrome debug connection and then hangs until the job timeout.

Could you remove the chromedriver flutter drive -d chrome steps from both the Linux and Windows desktop jobs? We still retain Chrome browser coverage through flutter test --platform chrome / flutter pub run test -p chrome, desktop integration coverage through flutter test integration_test/... -d linux/windows/macos, Firefox coverage, and the new Linux dart2wasm smoke job. So this removes the flaky duplicate WebDriver path rather than removing unique package coverage.

[HamdaanAliQuatil]

lgtm. all tests pass. thanks!

we should add a longer per-test timeout to the native macOS integration step, probably matching Android.

[harrshita123]

lgtm. all tests pass. thanks!

we should add a longer per-test timeout to the native macOS integration step, probably matching Android.

lgtm. all tests pass. thanks!

we should add a longer per-test timeout to the native macOS integration step, probably matching Android.

I’ll update that and add a longer timeout for the native macOS integration step as well.