-
Notifications
You must be signed in to change notification settings - Fork 93
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
test: ensure test suite is passing on windows (wsl) #1451
Comments
If I'm reading this correctly, we can't run WSL2 on an EC2 Windows instance because it doesn't support nested virtualization, same issue that used to be present in the GH runners. We may have to wait until the actions/runner-images folks get to my request for enabling WSL 2 before we can complete this. |
I don't think we have any paths forward until WSL 2 is enabled in github hosted runners. |
Using the Azure instance instead of AWS to do this. Description has been updated. |
|
You can use https://github.com/vedantmgoyal9/setup-wsl2. |
For some projects under github.com/ansible and github.com/ansible-collections we use Azure Pipelines for testing against different Windows versions, this integrates well with GitHub's CI reporting We could have a specific Azure Pipelines jobs that only runs windows. We have a decent amount of Azure Pipeline capacity for running jobs. |
Currently we are not test
ui
ande2e
on CI because:task ui
ortask e2e
is crashing windows runners with ambiguous message below:We did switch from default windows-2022 (8GB RAM) to enlarged 16GB one but without any visible change.
Next step would to setup a permanent self-hosted windows based github runner on AWS and use this one for testing. This should also allow us to connect to the machine directly and see why it was crashing.
Tasks
The text was updated successfully, but these errors were encountered: