-
Notifications
You must be signed in to change notification settings - Fork 27
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
CI: Windows tests fail randomly with current runner image #39
Comments
Self-hosted runner on Windows 10 failed to run job, see https://github.com/sebastianhaberey/nsd/actions/runs/4445462134/jobs/7804618812. |
The last successful run was based on commit 32d7a1a which corresponds to plugin version 2.2.3 (2.2.2 was a broken version). |
Older Plugin versions (2.2.3, 2.3.0) fail on the current runner, too. |
Since this seems to be related to the Windows Server 2000 environment, which is not a very likely platform for the plugin to run on, and the tests pass in an Windows 10 environment, I am removing the Windows badge from the documentation until the CI succeeds again (maybe with new versions of the Github runner) or there is a way to run Github actions on Windows 10/11. |
I decided to leave this open as a reminder that the Windows CI is broken. |
Won't fix for now, see issue #41 |
Description
Windows tests fail on current CI on runner
windows-2022
image tagwin22/20230307.2
which contains Windows Server 202210.0.20348 Build 1547. The tests that fail vary from run to run, but at least one test fails. These tests are run automatically if Windows sources change, or manually. Last successful run was on 06.06.2022 on runnerwindows-2022
image tagwin22/20220529.1
which contains Windows Server 2022 10.0.203348 Build 707.It doesn't seem possible to revert runner images to previous versions and I don't have a live Windows Server 2022 installation to test this. Tests pass reliably on current Windows 10 (10.0.19045.2673) machine (see below).
Test output on Windows 10 test machine (3 runs)
Flutter doctor output on Windows 10 test machine
Scenario
Other (please describe above)
Platform
Windows
The text was updated successfully, but these errors were encountered: