Pavel Feldman

Make sure you are using the same version of Playwright in your packages. Npm will perform all the necessary deduplication. You can find the source of the problem via examining...

There isn't much we can do without the repro. Are you saying it is a regression relative to 1.44?

Do you think you can achieve the same better behavior with your sharding seed? Or are you looking for additional bias against subsequent tests being put into the same group?

I think your seed change allows users to experiment with the seeds and arrive at some better state than they are today. Any other changes w/o the timing feedback are...

> I was thinkings about adding a separate reporter for that purpose, but if those last run stats are already there…, then there might not be the need to create...

> I think it should only get written when it's actually running tests. Agreed. Note that for the PGO-alike behavior, we would probably explicitly point to the file and commit...

Your browser is running out of memory or out of handles when trying to allocate a bitmap: https://source.chromium.org/chromium/chromium/src/+/main:ui/views/win/hwnd_message_handler.cc;l=2515;drc=3e02eb658e84b46ebb53667e0a1cb52fe53b5f87;bpv=1;bpt=1 What is the host system resolution? `--start-maximized` might be too much for...

Not sure what it happening then - OS refuses to return a display handle to the browser. Being able to reproduce it would help, otherwise there isn't much we can...

I'm going to close it as non-actionable on our side since there are no other reports similar to yours and there is no way for us to repro it.

What is `CHROMIUM_BIN`? It is not a part of Playwright or something Playwright supports. You should not call `npx playwright install` if you are bringing your own browser.