Bug 183737 - Facing org.openqa.selenium.WebDriverException while running safariDriver in Mac
Summary: Facing org.openqa.selenium.WebDriverException while running safariDriver in Mac
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebDriver (show other bugs)
Version: Safari 11
Hardware: PC macOS 10.13
: P1 Critical
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-19 01:38 PDT by shariqMohammed
Modified: 2018-03-19 09:06 PDT (History)
1 user (show)

See Also:


Attachments
exception faced (204.64 KB, image/png)
2018-03-19 01:38 PDT, shariqMohammed
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description shariqMohammed 2018-03-19 01:38:41 PDT
Created attachment 336034 [details]
exception faced

Error: org.openqa.selenium.WebDriverException: An unknown server-side error occurred while processing the command. (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 0 milliseconds
Build info: version: '3.11.0', revision: 'e59cfb3', time: '2018-03-11T20:26:55.152Z'
System info: host: 'Admins-Mac-mini.local', ip: '192.168.11.72', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.13.1', java.version: '1.8.0_144'
Driver info: org.openqa.selenium.safari.SafariDriver

The timeout duration is shown to be ## 0 milliseconds.

Meta -

OS: macOS HighSierra v10.13.1
Browser: Safari v11.0.1
Comment 1 BJ Burg 2018-03-19 09:06:10 PDT
Please file safaridriver bugs to https://bugreport.apple.com/

Additionally, you have not provided any useful information, so I can't help you. Perhaps include the following:

Is this behavior reproducible in Safari Technology Preview (STP)? https://developer.apple.com/safari/technology-preview/

Include versions of Selenium or other WebDriver client libraries, Safari, safaridriver, macOS.

Describe the failing command and its inputs and outputs.

Did this behavior occur in a previous release of Safari?
Does this behavior occur in other browsers (Firefox, Chrome, Edge)?
What language is the test written in?
Do you use Selenium Grid, SauceLabs, BrowserStack, or other scaling infrastructure?

If possible include a Webarchive of the page as it was when the command failed, a test page accessible to Apple engineers, and the test case itself.