vscode: All Web Smoke tests fail for me under Linux

Testing #127395

The Web smoke test all failed for me. @aeschli tried as well on his native Linux machine with the same outcome.

Insider build used: cc52823098

~~According to @aeschli smoke test passes with latest stable (1.57.1)~~

Assigning to @bpasero and @lszomoru

About this issue

This was a bit expensive (as it took me quite a while to get the setup), but here is what I observed:

I downladed the build cc52823098 -> vscode-server-linux-x64-web.tar.gz
(I did not have WSL configured with x windows)
- when I executed yarn smoketest --build ~/src/vscode-server-linux-x64-web --web --browser chromium I saw the same hangs that @dbaeumer reported
- I tried to launch yarn smoketest --build ~/src/vscode-server-linux-x64-web --web --browser chromium --debug but everything kept on hanging and I could not see the browser
so I went and followed all the steps at https://github.com/microsoft/vscode/wiki/Selfhosting-on-Windows-WSL . I did not do those steps previously
those steps were incomplete, I also had to execute sudo apt-get install -y libgbm-dev to get ./scripts/code.sh to work and I had to manually allow the xserver even on public networks 🤷‍♂️ .
finally after doing all that setup, now the smoketest passes for me and I get to always see it even when invoking without --debug, so I think there might be something off with playwright under WSL where it always decides to show the browser. AFAIK it should only show the browser when invoking with --debug.

In any case, @dbaeumer , this works for me. Here is a video to show that it is working for me:

@joaomoreno I think you already have this setup, can you please confirm if you reproduce what @dbaeumer is seeing or if smoketests run for you?

This appears related to @lszomoru’s good change to isolate each suite in its own session. We should find where that breaks down.

Ok thanks, then maybe Dirk and you could chat how to unblock him. It looks like this maybe a setup problem.