BrowserCommandControllerInteractiveTest.ShortcutsShouldTakeEffectInJsFullscreen flaky on Windows |
||
Issue descriptionIt times out every once in a while with very little info to go on: [ RUN ] BrowserCommandControllerInteractiveTest.ShortcutsShouldTakeEffectInJsFullscreen [5180:5932:1128/173222.751:WARNING:chrome_browser_main_win.cc(613)] Command line too long for RegisterApplicationRestart: --brave-new-test-launcher --cfi-diag=0 --gtest_also_run_disabled_tests --gtest_filter=BrowserCommandControllerInteractiveTest.ShortcutsShouldTakeEffectInJsFullscreen --single_process --snapshot-output-dir="e:\b\s\w\io3n9xbo" --test-launcher-bot-mode --test-launcher-output="C:\Users\CHROME~2\AppData\Local\Temp\scoped_dir4580_25040\results4580_23491\test_results.xml" --test-launcher-summary-output="e:\b\s\w\io3n9xbo\output.json" --user-data-dir="C:\Users\CHROME~2\AppData\Local\Temp\scoped_dir4580_25040\d4580_30306" --disable-offline-auto-reload --no-first-run --no-default-browser-check --enable-logging=stderr --disable-default-apps --wm-window-animations-disabled --disable-component-update --test-type=browser --force-color-profile=srgb --disable-zero-browsers-open-for-tests --ipc-connection-timeout=30 --allow-file-access-from-files --dom-automation --log-gpu-control-list-decisions --disable-backgrounding-occluded-windows --disable-gl-drawing-for-tests --override-use-software-gl-for-tests --force-color-profile=srgb --enable-features=TestFeatureForBrowserTest1 --disable-features=NetworkPrediction,TestFeatureForBrowserTest2 --flag-switches-begin --flag-switches-end --restore-last-session about:blank [115/275] BrowserCommandControllerInteractiveTest.ShortcutsShouldTakeEffectInJsFullscreen (TIMED OUT) I'll send up a CL to grab a snapshot of the screen when it times out. Maybe that'll help explain what's going on.
,
Nov 29 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fbe8c9a11f561c42fcc2d5d4218b887216719758 commit fbe8c9a11f561c42fcc2d5d4218b887216719758 Author: Greg Thompson <grt@chromium.org> Date: Wed Nov 29 20:10:06 2017 Always save screen snapshots when tests time out. BUG= 789537 R=sky@chromium.org Change-Id: I938ca44ab2f5ad87600dba98de257425d30d2f5f Reviewed-on: https://chromium-review.googlesource.com/796415 Reviewed-by: Scott Violet <sky@chromium.org> Commit-Queue: Greg Thompson <grt@chromium.org> Cr-Commit-Position: refs/heads/master@{#520214} [modify] https://crrev.com/fbe8c9a11f561c42fcc2d5d4218b887216719758/chrome/test/base/always_on_top_window_killer_win.cc [modify] https://crrev.com/fbe8c9a11f561c42fcc2d5d4218b887216719758/chrome/test/base/always_on_top_window_killer_win.h [modify] https://crrev.com/fbe8c9a11f561c42fcc2d5d4218b887216719758/chrome/test/base/interactive_ui_tests_main.cc
,
Nov 29 2017
I see flakes on Win7 Tests (1) and Win 7 Tests x64 (1); see https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=interactive_ui_tests&tests=BrowserCommandControllerInteractiveTest.ShortcutsShouldTakeEffectInJsFullscreen.
,
Dec 6 2017
It's stopped flaking. Maybe the flakes were caused by the missing CHROME_HEADLESS=1, which is now resolved. Closing for now. |
||
►
Sign in to add a comment |
||
Comment 1 by zijiehe@chromium.org
, Nov 29 2017