Failing layout test results (layout-test-results/results.html) opens in Safari instead of Chrome |
||||
Issue descriptionWhen running run-webkit-tests on a failing test, Safari now opens with the results. Previously, Chrome would open with the test results. You will need to find a test that fails or intentionally cause a crash to reproduce this bug. OS: MacOS Sierra 10.12.5 (16F73) I'm running the layout test like so: ------------------------8<------------------------ [12:14:28]:~/Desktop/chromium/src $ ./third_party/WebKit/Tools/Scripts/run-webkit-tests --debug fast/forms/calendar-picker/week-picker-ax.html Using port 'mac-mac10.12' Test configuration: <mac10.12, x86, debug> View the test results at file:///Users/pdr/Desktop/chromium/src/out/Debug/layout-test-results/results.html View the archived results dashboard at file:///Users/pdr/Desktop/chromium/src/out/Debug/layout-test-results/dashboard.html Using random order with seed: 1497813355 Baseline search path: mac -> generic Using Debug build Pixel tests enabled Regular timeout: 18000, slow test timeout: 90000 Command line: /Users/pdr/Desktop/chromium/src/out/Debug/Content Shell.app/Contents/MacOS/Content Shell --run-layout-test - Found 1 test; running 1, skipping 0. Running 1 Content Shell. [1/1] fast/forms/calendar-picker/week-picker-ax.html failed unexpectedly (renderer crashed) Summarizing results ...0:97: execution error: "file:///Users/pdr/Desktop/chromium/src/out/Debug/layout-test-results/results.html" doesn’t understand the “open location” message. (-1708) 70:78: execution error: Can’t get application "firefox". (-1728) 0 tests ran as expected, 1 didn't: Regressions: Unexpected crashes (1) fast/forms/calendar-picker/week-picker-ax.html [ Crash ] ------------------------8<------------------------ The line "execution error: Can’t get application "firefox"." looks new to me.
,
Jun 19 2017
This is a bug of macOS 10.12.5. See https://bugs.python.org/issue30392 Workaround: specify $BROWSER. e.g. export BROWSER=/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome
,
Jun 21 2017
,
Dec 15 2017
pdr@, is this still happening on a more recent macOS?
,
Dec 18 2017
I see that pdr@ is OOO until March, so I'll assume the bug is still there and mark it as available.
,
Mar 26 2018
I think this is fixed in High Sierra (based on my observation and the discussion in the Python issue tracker linked in #2). Feel free to reopen if you see the error again. |
||||
►
Sign in to add a comment |
||||
Comment 1 by pdr@chromium.org
, Jun 18 2017