Has anybody an idea why Jenkins UI tests fail in our CI instance since a couple
of days due to a org.openqa.selenium.json.JsonException?
Caused by: org.openqa.selenium.json.JsonException: Expected to read a START_MAP
but instead have: END. Last 0 characters read:
Build info: version: '3.141.59', revision: 'e82be7d358', time:
'2018-11-14T08:17:03'
System info: host: 'ip-172-31-21-171', ip: '172.31.21.171', os.name: 'Linux',
os.arch: 'amd64', os.version: '5.8.0-1038-aws', java.version: '11.0.6'
Driver info: driver.version: RemoteWebDriver
at org.openqa.selenium.json.JsonInput.expect(JsonInput.java:290)
at org.openqa.selenium.json.JsonInput.beginObject(JsonInput.java:220)
at
org.openqa.selenium.json.MapCoercer.lambda$apply$1(MapCoercer.java:64)
at
org.openqa.selenium.json.JsonTypeCoercer.lambda$null$6(JsonTypeCoercer.java:145)
at
org.openqa.selenium.json.JsonTypeCoercer.coerce(JsonTypeCoercer.java:126)
at org.openqa.selenium.json.Json.toType(Json.java:69)
at org.openqa.selenium.json.Json.toType(Json.java:55)
at org.openqa.selenium.json.Json.toType(Json.java:50)
at
org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:112)
... 74 more
Examples:
-
https://ci.jenkins.io/job/Plugins/job/warnings-ng-plugin/job/PR-1010/1/testReport/io.jenkins.plugins.analysis.warnings/SmokeTests/linux_11___Build__linux_11____shouldRecordIssuesInPipelineAndExpandTokens/
<https://ci.jenkins.io/job/Plugins/job/warnings-ng-plugin/job/PR-1010/1/testReport/io.jenkins.plugins.analysis.warnings/SmokeTests/linux_11___Build__linux_11____shouldRecordIssuesInPipelineAndExpandTokens/>
-
https://ci.jenkins.io/job/Plugins/job/git-forensics-plugin/job/master/lastCompletedBuild/testReport/io.jenkins.plugins.forensics/ForensicsPluginUiTest/linux_11___Build__linux_11____shouldAggregateToolsIntoSingleResult/
<https://ci.jenkins.io/job/Plugins/job/git-forensics-plugin/job/master/lastCompletedBuild/testReport/io.jenkins.plugins.forensics/ForensicsPluginUiTest/linux_11___Build__linux_11____shouldAggregateToolsIntoSingleResult/>
After switching from chrome-driver to firefox-driver at least Jenkins CI seems
to work again (GitHub actions still fail).
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/DDA7BA15-31A4-4EF9-A876-62AF7AF36DB9%40gmail.com.
