Skip to content
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

Open
4 tasks
ssbarnea opened this issue Jul 24, 2024 · 6 comments
Open
4 tasks

test: ensure test suite is passing on windows (wsl) #1451

ssbarnea opened this issue Jul 24, 2024 · 6 comments
Labels
bug Something isn't working important

Comments

@ssbarnea
Copy link
Member

ssbarnea commented Jul 24, 2024

Currently we are not test ui and e2e on CI because:

  • github hosted windows runners are not supporting WSL2, docker and podman (no nested virtualization
  • executing task ui or task e2e is crashing windows runners with ambiguous message below:

The hosted runner: devtools-win-x64_04594ca6558b lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

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

Preview Give feedback
@ssbarnea ssbarnea added the bug Something isn't working label Jul 24, 2024
@ssbarnea ssbarnea pinned this issue Jul 24, 2024
@alisonlhart alisonlhart moved this from Roadmap to In Progress in 🧰 devtools project board Aug 27, 2024
@alisonlhart
Copy link
Contributor

alisonlhart commented Sep 19, 2024

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.
I'm seeing that issue right now when I try to configure the new instance to use WSL 2.

We may have to wait until the actions/runner-images folks get to my request for enabling WSL 2 before we can complete this.

@alisonlhart alisonlhart moved this from In Progress to Roadmap in 🧰 devtools project board Sep 19, 2024
@alisonlhart alisonlhart moved this from Roadmap to In Progress in 🧰 devtools project board Sep 19, 2024
@alisonlhart
Copy link
Contributor

I don't think we have any paths forward until WSL 2 is enabled in github hosted runners.

@alisonlhart
Copy link
Contributor

Using the Azure instance instead of AWS to do this. Description has been updated.

@alisonlhart
Copy link
Contributor

shell: bash will not work for windows runners using WSL. Continuing to research and try other options.
See: actions/runner#1328

@vedantmgoyal9
Copy link

You can use https://github.com/vedantmgoyal9/setup-wsl2.

@gundalow
Copy link

gundalow commented Dec 6, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working important
Projects
Status: In Progress
Development

Successfully merging a pull request may close this issue.

4 participants