mercredi 3 juin 2020

Selenium gets itself into a loop and constantly closes its windows [duplicate]

I have a test suite that's running on Jenkins CI on an AWS instance. It's using Ruby 2.2.9 and Rails 4.2.1, Capybara 2.18, Chrome 75, and chromedriver 2.46. Sometimes, but unfortunately not repeatably, Jenkins will get itself into a state that we don't know how to recover from -- other than rebooting the instance. When it gets like this, many of the specs fail with this error:

07:18:06             Selenium::WebDriver::Error::NoSuchWindowError:
07:18:06               no such window: window was already closed
07:18:06                 (Session info: headless chrome=75.0.3770.80)
07:18:06                 (Driver info: chromedriver=2.46.628388 

No amount of searching for this error has brought up anything that is actionable for our case. The major difference between CI and development is that, locally, we all develop on MacOS whereas Jenkins is running Linux.

Has anyone seen anything like this before and/or can point me in a direction that can help solve this?

Aucun commentaire:

Enregistrer un commentaire