Open saschanaz opened 2 years ago
Adding --log-mach - --log-mach-level info
as suggested by @gsnedders the output contains (with level WARNING
):
webdriver.error.SessionNotCreatedException: session not created (500): Could not create a session: You must enable the 'Allow Remote Automation' option in Safari's Develop menu to control Safari via WebDriver.
The grouped logger only outputs ERROR and CRITICAL logs, thus safaridriver
giving a useful error message totally gets swallowed by our logging config.
It would probably be good to make some of the startup warnings into errors, and maybe handle webdriver.error.SessionNotCreatedException
specifically (because a traceback there isn't very useful in that context, but the message probably is).
That said, it's not totally obvious how to do this without breaking abstraction given executors.protocol
is the one that does all the logging when an exception is thrown.
Hard to see the problem as https://web-platform-tests.org/running-tests/safari.html doesn't have it and the message gives no reason why the restart happened. The docs should have it at least, and I wonder the error message can be better.