[BUG] browserContext.storageState times out

[WcaleNieWolny]

System info

• Playwright Version: ^1.40.0
• Operating System: ubuntu-latest (Github actions CI/CD)
• Browser: Chromium
• Other info: Might be difficult to reproduce as I was only ever able to get this error on the CI/CD. Reproducing the CI/CD setup locally is quite difficult.

Source code

• https://github.com/WcaleNieWolny/capgo/tree/organization-system/tests

• [ ] I provided exact source code that allows reproducing the issue locally. Well, not exactly. Cannot reproduce locally tho the CI/CD gets this error almost every time. I had 1 run that failed with this exact issue, then a successful one and again this but.

Here is the github PR that has the tests failing. The CI/CD setup for that is quite complex but essentialy what is failing is the browserContext.storageState. For whatever reason this timeouts after 3 minutes. An important details is that I start the playwright process multiple times.

For example as you can see in the test run for "Fix select" commit there is a `Running test (1/1): "Test frontend" message. What that essentialy means is that playwright gets spawned as a child process of my custom testing framework.

That is defined here

However, more importantly what fails is the browserContext.storageState

I have downloaded the trace and video but I am unable to access trace. This is very similar to this issue

As for the video, I am able to access it. It shows that the entire auth flows goes exacly as I intended and that every single step that my app should take was taken.

Here is the video:

b223937fe08ad78b4d8bf02ebc536697a3ad7fb5.webm

Additionally here are the steps shown in the report viewer

Link to the GitHub repository with the repro

https://github.com/WcaleNieWolny/capgo/tree/organization-system/tests

Config file

See here

Test file (self-contained)

Cannot provide, please see above

Steps Again, see above

Expected

browserContext.storageState to NEVER timeout

Actual

browserContext.storageState times out after 3 minutes

[mxschmitt]

This looks very similar to https://github.com/microsoft/playwright/issues/28319. Could you try version 1.39 and see if you can reproduce it there?

npx playwright --version to verify that you are using v1.39.

[WcaleNieWolny]

Thanks for your swift response, I changed the playwright version into 1.39 as you recommended and the error seams to be gone. For now I am going to close this and I am going to subscribe to the issue you linked.