Description
System info
- Playwright Version: v1.33
- Operating System: Windows 10
- Browser: Chromium 114
- Other info: Selenium Server 4.8.3
Steps
- Run playwright test on selenium hub with nodes
- Selenium node default session timeout: for example 300 seconds
- Maybe reproduceable by adding a Task.Delay() to the tests so that the test exceeds the 300 seconds
Expected
I think it's due to the communication between Playwright and Selenium. If Selenium exits the test after the "session-timeout", then Playwright should abort the test.
Actual
Playwright continues test even selenium has ended the session.
Description
I've seen the problem more than once. The test starts and runs interactions. At some point the test gets stuck, Playwright does not abort the test (added the Playwright timeouts, 30000ms, and in most cases the tests will be aborted, for example if no element was found). The Selenium node ends the session after the selenium session timeout, e.g. 5 minutes ("session-timeout" is configurable when starting the node). After Selenium has stopped the session, Playwright doesn't seem to get any feedback that the session has ended and the test continues indefinitely.