Closed mastrzyz closed 1 week ago
I have a hunch!
could it be due to this NOT awaiting any of its
expect(
page.getByTestId(`people-picker-no-results`)
).toBeVisible();
``` ?
It has 4 of them
await
is missing before the expect call:
await expect(
page.getByTestId(`people-picker-no-results`)
).toBeVisible();
You can consider adding lint rules to avoid non-awaited promises.
@yury-s the ask here is to have Playwright more gracefully close/stop . Is it expected behavior to have a worker error here?
@yury-s does that seem fair? I understand that there is a lint rule but that can be bypassed easily unfortunately.
Version
1.47.2
Steps to reproduce
This is very hard to reproduce locally, I have only seen it in CI at around ~95% repeatability
Expected behavior
The following code passes/fails without bringing down the worker
Actual behavior
AFTER
Failed worker ran 4 tests:
Additional context
No response
Environment
System: OS: Windows 11 10.0.26100 CPU: (20) x64 Intel(R) Core(TM) i9-10900X CPU @ 3.70GHz Memory: 21.61 GB / 47.72 GB Binaries: Node: 20.11.1 - C:\Program Files\nodejs\node.EXE Yarn: 1.22.21 - ~\AppData\Roaming\npm\yarn.CMD npm: 10.2.4 - C:\Program Files\nodejs\npm.CMD bun: 1.1.4 - ~.bun\bin\bun.EXE IDEs: VSCode: 1.95.1 - C:\Users\REMOVED\AppData\Local\Programs\Microsoft VS Code\bin\code.CMD Languages: Bash: 5.1.16 - C:\WINDOWS\system32\bash.EXE