Hi Pablo,
Here’s the good news, I suspect your issue has nothing to do with Jenkins, and everything to with chrome, chromedriver and seleniumlibrary
This pretty much proves that Jenkins ran robot framework and Jenkins got the correct response from the ran robot framework test (the test failed)
Most commonly when I see this error:
It’s because chrome has auto-updated itself and you haven’t updates the chrome WebDriver, I see you did your best to ensure the versions the same 
but you might have been unlucky and got caught out on release day?
Monday, March 27, 2023
The Stable channel has been updated to 111.0.5563.147 for Mac and Linux and 111.0.5563.146/.147 for Windows
If you’re sure that chrome didn’t auto-update itself, you might have been unlucky with your chrome WebDriver version, seems from the release notes there were issues with Chromedriver version 110.0.5481.77:
ChromeDriver 112.0.5615.28
Supports Chrome version 112
- Resolved issue 4357: Chromedriver version 110.0.5481.77 session issue with --headless and --user-data-dir options. [Pri-1]
I’ve also had issues in the past with ChromeDriver being less than Chrome even in the subminor version, in your case you are 77 vs 177, and 77 is the latest version in the 110.0.5481 range so it “should” work but not always
ChromeDriver 110.0.5481.77
Chrome 110.0.5481.177
I’ll suggest you try again with chrome/chromedriver 111.0.5563.x before wasting too much time on anything else
I’ve also had that error error: Chrome failed to start: exited abnormally. when I had a buggy version of chrome that was actually crashing on launch or when chromedriver crashed on launch (not for a long time though)
Hopefully some of this is helpful,
Dave.