-
Notifications
You must be signed in to change notification settings - Fork 10.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[windows][toolchain] Run Swift Runtime execution tests in x86_64 Android emulator #79081
base: main
Are you sure you want to change the base?
[windows][toolchain] Run Swift Runtime execution tests in x86_64 Android emulator #79081
Conversation
I expect to see the same issues with the Android Emulator in CI as in #78762. I will get back to that next week. Results I get locally:
|
Nice, any reason you only ran about 34 tests from the compiler validation suite locally? It would be great if the Windows CI ran more of those, alongside the new proposed Android community CI that runs everything but the executable tests on linux, swiftlang/swift-community-hosted-continuous-integration#55, ie those tests that don't require the emulator. |
Thanks for your note. This is an early version for a minimal subset of tests. Idea was to get the emulator approach evaluated early, because it would take longer to stabilize in CI. Non-execution tests will follow. This will add a substantial amount of test runtime. I guess we will need to figure out how much of it we run in CI regularly. |
Most non-executable tests failed because
|
Let's see if we can reproduce this in CI |
@swift-ci please test Windows |
The build failed for an unrelated reason (flake in LLDB). Enabled AndroidSDK x86_64 now (and disable unrelated tests). Let's try again. @swift-ci please test Windows |
Pass rate on CI machines is much lower:
I will check the logs and investigate. |
Actually, not a good idea to mix these up. I will do the non-executable tests in #79185 and keep this PR focussed on execution tests. |
First version for early feedback