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
{{ message }}
Repository navigation
[Windows Arm64] Run existing devicelab tests on Arm64 #129806
Currently, Windows integration tests run on x64 Devicelab machines.
Solution
Once #129805 lands, the Flutter tool will be able to produce x64 executables on Arm64 machines. Existing Windows Devicelab and perf tests should be updated to run Arm64 machines using x64 emulation.
The Android Devicelab tests will also need to be updated to run on an Windows Arm64 host, tracked by #136378.
Devicelab tests that target Windows Arm64 are now enabled. The remaining work of enabling Devicelab tests that target Android from a Windows Arm64 host is tracked by #136378
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
[Windows] Add more Arm64 compile and run tests (#135475)
[Windows] Add more Arm64 compile and run tests (flutter#135475)
loic-sharma commentedon Sep 28, 2023
Benchmarks are blocked by #135722
[Windows] Add first Arm64 plugin tests (#135512)
[Windows] Add more Arm64 compile and run tests (flutter#135475)
[Windows] Add first Arm64 plugin tests (flutter#135512)
[Windows] Add Arm64 benchmarks (#135514)
[Windows Arm64] Add the 'platform_channel_sample_test_windows' Device…
loic-sharma commentedon Oct 12, 2023
Devicelab tests that target Windows Arm64 are now enabled. The remaining work of enabling Devicelab tests that target Android from a Windows Arm64 host is tracked by #136378
Squash of flutter-preview-device-3 branch:
github-actions commentedon Oct 26, 2023
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.