You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A clear and concise description of what the bug is.
After running any side file the regardless if successful or not I get an error and it takes from 10 seconds up to a minute until the command has finished.
Jest did not exit one second after the test run has completed.
'This usually means that there are asynchronous operations that weren't stoppedin your tests. Consider running Jest with --detectOpenHandles to troubleshootthis issue.
Yeah I'm seeing that too. Not ideal. Will be looking at it this weekend or next. First thing on my slate is doing a bit of changes to the new internationalization system to align that stuff more long term (we are getting some absolutely amazing help from some Chinese developers). After that's out, I'll come back around here.
馃悰 Bug Report
A clear and concise description of what the bug is.
After running any side file the regardless if successful or not I get an error and it takes from 10 seconds up to a minute until the command has finished.
Jest did not exit one second after the test run has completed.
'This usually means that there are asynchronous operations that weren't stoppedin your tests. Consider running Jest with
--detectOpenHandles
to troubleshootthis issue.To Reproduce
npm init
npm i selenium-side-runner@^4.0.5
./node_modules/.bin/selenium-side-runner -c 'browserName=chrome goog:chromeOptions.args=[headless,disable-infobars,disable-gpu,no-sandbox,disable-dev-shm-usage]' -s http://localhost:4444/wd/hub /projects/mpoint/webdriver/test/wuedesto/Wuedesto_DE-Login-Logout.side
I am using Selenium 4.20.0 with Chrome 120.
Expected behavior
The system should run without error
Environment
OS: Debian
Selenium IDE Version: 4.2.0
Selenium SIDE Runner Version: 4.0.5
Please note that selenium-side-runner supports Node.js 16+
-->
Node version: 20.12.2
Only required if using selenium-side-runner
-->
Browser: Chrome 120.0.6099.199
The text was updated successfully, but these errors were encountered: