Hi folks. We have some selenium-based tests that have been fairly stable for a while, but in the past few months there have been a few failures due to connection pool timeouts with the database, timeouts with the webdriver assertion, etc. We can run these tests locally and they pass just fine. Furthermore, we used to just re-run these tests from failure in the Circle dashboard, and they’d eventually pass. But it’s gotten progressively worse over time, to the point we’re at now where it’s a less than 50% chance that the test will pass. I’ve tried optimizing by splitting the jobs into parallel workflows, but it doesn’t seem to make a difference.
Is it possible that our use of the docker executor type combined with additional load on the worker instance we’re using is causing these timeouts? If so, what solution do you recommend?
Kind regards,
Joe