-
Notifications
You must be signed in to change notification settings - Fork 3.7k
infrastructure/ tests don't work with Safari Technology Preview 68 #13800
Copy link
Copy link
Closed
Labels
Description
In #13769, STP is being pinned to 67, because STP 68 doesn't seem to work. The configuration was developed in foolip#7, and https://dev.azure.com/foolip/wpt/_build/results?buildId=112&view=logs is a build from when STP 68 was used. The logs contain this over and over:
0:45.55 DEBUG new state: initializing_browser
0:45.55 DEBUG Dispatch init
0:45.56 DEBUG Init called, starting browser and runner
0:45.56 DEBUG Starting browser with settings {}
0:45.56 DEBUG Starting WebDriver: /Applications/Safari Technology Preview.app/Contents/MacOS/safaridriver --port=4444
0:45.56 DEBUG Waiting for WebDriver to become accessible: http://127.0.0.1:4444/
1:00.95 ERROR WebDriver was not accessible within the timeout:
Traceback (most recent call last):
File "/Users/vsts/agent/2.141.1/work/1/s/tools/wptrunner/wptrunner/webdriver_server.py", line 73, in _run
wait_for_service((self.host, self.port))
File "/Users/vsts/agent/2.141.1/work/1/s/tools/wptrunner/wptrunner/webdriver_server.py", line 265, in wait_for_service
raise socket.error("Service is unavailable: %s:%i" % addr)
error: Service is unavailable: 127.0.0.1:4444
@burg, are you aware of any trouble with SafariDriver with STP 68?
Reactions are currently unavailable