[Bug]: After updating to 1.50, it happens that Worker Cleanup job take a lot of time (more than 2/3 minutes) when test are failing. (UI mode)

[samixchoumi]

Version

1.50.0

Steps to reproduce

Just have failing tests, it happens sometime. (Using UI mode)
Similar behavior happen when you launch a series of test and then when they're all executed, the Run button is still not available if I don't hard kill the execution.

Expected behavior

Cleanup step is executed as fast as before.
Don't need to hard kill test execution to have the Run button available when the execution is already finished.

Actual behavior

As described in the Steps to reproduce. It wasn't the case before and their is no log in the terminal.

Additional context

Big E2E test project, I use UI mode.

Environment

System:
    OS: macOS 15.2
    CPU: (8) arm64 Apple M1 Pro
    Memory: 716.89 MB / 16.00 GB
  Binaries:
    Node: 23.5.0 - /usr/local/bin/node
    npm: 11.0.0 - /usr/local/bin/npm
    pnpm: 8.10.3 - /usr/local/bin/pnpm
  IDEs:
    VSCode: 1.88.1 - /opt/homebrew/bin/code # I'm using IntelliJ
  Languages:
    Bash: 3.2.57 - /bin/bash # I'm using Typescript
  npmPackages:
    @playwright/test: ^1.50.0 => 1.50.0 
    playwright-bdd: ^8.1.0 => 8.1.0 
    playwright-slack-report: ^1.1.89 => 1.1.89

[dgozman]

We need more information to act on this issue. Could you please provide a repro that we can run locally?

[samixchoumi]

I can't send access to our company project, but I will try to do a little github project that reproduce it (but as I mentioned, it's not happening every time ...)

[samixchoumi]

@dgozman https://github.com/samixchoumi/issue_34598_playwright_example here you can find a project sample where I reproduced the issue multiple time.

[dgozman]

@samixchoumi Thank you for the repro. Unfortunately, I was not able to reproduce after running 20 times with/without UI mode. Note that I have removed playwright-slack-report when reproducing. Perhaps it could be a culprit?

[samixchoumi]

Let me check without it, if it’s the case it’s strange because I didn’t changed anything regarding this report, it was already this version before upgrading playwright to 1.50.0

…

On Tue, Feb 4, 2025 at 13:01 Dmitry Gozman ***@***.***> wrote: @samixchoumi <https://github.com/samixchoumi> Thank you for the repro. Unfortunately, I was not able to reproduce after running 20 times with/without UI mode. Note that I have removed playwright-slack-report when reproducing. Perhaps it could be a culprit? — Reply to this email directly, view it on GitHub <#34598 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFJFCGE72FXGBSC5ZD4I5ZD2OCTZTAVCNFSM6AAAAABWMRK6RSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZTGY4TONZYGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[samixchoumi]

I still reproduce without this package.

[dgozman]

I still reproduce without this package.

Unfortunately, that does not help me to reproduce the issue. A few ideas I have:

• run npx playwright clear-cache;
• run with DEBUG=pw:test env variable and share the logs here;
• run with PWTEST_PROFILE_DIR=./profiles env variable and share json files from the profiles directory here.