[JIRA] (JENKINS-60102) Getting "unexpected modal dialog" exception

12 views
Skip to first unread message

vincent@latombe.net (JIRA)

unread,
Nov 8, 2019, 4:39:03 AM11/8/19
to jenkinsc...@googlegroups.com
Vincent Latombe created an issue
 
Jenkins / Bug JENKINS-60102
Getting "unexpected modal dialog" exception
Issue Type: Bug Bug
Assignee: Oliver Gondža
Components: acceptance-test-harness
Created: 2019-11-08 09:38
Priority: Major Major
Reporter: Vincent Latombe

When upgrading acceptance-test-harness I get the following exception.

Caused by: org.openqa.selenium.UnhandledAlertException: Unexpected modal dialog (text: blabla): blabla
[redacted]
Session ID: bf00ad4e-12aa-4ee5-a6d7-a97ecdedb577
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
	at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:214)
	at org.openqa.selenium.remote.ErrorHandler.createUnhandledAlertException(ErrorHandler.java:195)
	at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:156)
	at org.openqa.selenium.remote.http.JsonHttpResponseCodec.reconstructValue(JsonHttpResponseCodec.java:40)
	at org.openqa.selenium.remote.http.AbstractHttpResponseCodec.decode(AbstractHttpResponseCodec.java:80)
	at org.openqa.selenium.remote.http.AbstractHttpResponseCodec.decode(AbstractHttpResponseCodec.java:44)
	at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:158)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:548)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:605)
	at org.openqa.selenium.remote.RemoteWebDriver.getWindowHandle(RemoteWebDriver.java:468)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at org.openqa.selenium.support.events.EventFiringWebDriver.lambda$new$1(EventFiringWebDriver.java:105)
	at org.openqa.selenium.support.events.EventFiringWebDriver$$Lambda$196/965110781.invoke(Unknown Source)
	at com.sun.proxy.$Proxy35.getWindowHandle(Unknown Source)
	at org.openqa.selenium.support.events.EventFiringWebDriver.getWindowHandle(EventFiringWebDriver.java:221)
	at org.jenkinsci.test.acceptance.po.CapybaraPortingLayerImpl.handleAlert(CapybaraPortingLayerImpl.java:375)
	at org.jenkinsci.test.acceptance.po.CapybaraPortingLayerImpl.confirmAlert(CapybaraPortingLayerImpl.java:392)
[redacted]
	... 22 more

Looking around, it looks like it is caused by https://github.com/jenkinsci/acceptance-test-harness/pull/542, in particular https://github.com/jenkinsci/acceptance-test-harness/pull/542/files#diff-d0b6a61b36919ac2290b1ea8e74ee8f1R375

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

vincent@latombe.net (JIRA)

unread,
Nov 8, 2019, 4:39:03 AM11/8/19
to jenkinsc...@googlegroups.com
Vincent Latombe started work on Bug JENKINS-60102
 
Change By: Vincent Latombe
Status: Open In Progress

vincent@latombe.net (JIRA)

unread,
Nov 8, 2019, 4:39:04 AM11/8/19
to jenkinsc...@googlegroups.com
Vincent Latombe assigned an issue to Vincent Latombe
Change By: Vincent Latombe
Assignee: Oliver Gondža Vincent Latombe

ogondza@gmail.com (JIRA)

unread,
Nov 8, 2019, 5:00:02 AM11/8/19
to jenkinsc...@googlegroups.com

ogondza@gmail.com (JIRA)

unread,
Nov 8, 2019, 5:00:02 AM11/8/19
to jenkinsc...@googlegroups.com

vincent@latombe.net (JIRA)

unread,
Nov 8, 2019, 5:23:02 AM11/8/19
to jenkinsc...@googlegroups.com
Vincent Latombe edited a comment on Bug JENKINS-60102
[~olivergondza] It's a test from a CloudBees test harness so I can't share it directly, but I believe the cause is that the alert is already displayed when you are attempting to capture the window handle. I have provided a PR that should fix it.

vincent@latombe.net (JIRA)

unread,
Nov 8, 2019, 5:23:02 AM11/8/19
to jenkinsc...@googlegroups.com

Oliver Gondža It's a test from a CloudBees test harness so I can't share it directly, but I believe the cause is that the alert is already displayed when you are attempting the window handle. I have provided a PR that should fix it.

Reply all
Reply to author
Forward
0 new messages