Protocol error in Jenkins Pipeline

Hello all,

We are using robotframework with selenium for browser automation along with Pabot in jenkins pipeline.Getting error ProtocolError: (‘Connection aborted.’, ConnectionResetError(104, ‘Connection reset by peer’)) at random when trying to execute the tests in pipeline. Tests run sometimes and at times it fails with the above error. So unable to debug, any idea why it happens?

Setup failed: ProtocolError: (‘Connection aborted.’, ConnectionResetError(104, ‘Connection reset by peer’))
Skipped for Retry

There’s way too many possibilities that can trigger this error message. It could be due to memory limitations, way too small timeouts and bunch of others. Selenium 3.8 - 3.9 had bugs that caused this same error.

Your best option would be to enable full logging of webdriver itself, ensure that each log file gets unique name so that pabot execution wont overwrite the other runs logs and gther those logs as build artifacts after the testrun. If you had failures like that, you now also have logs from the webdriver itself that should at least help with isolating what caused the issue…

2 Likes