New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 591815 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

views_unittests.WidgetTest.SysCommandMoveOnNCLButtonDownOnCaptionAndMoveTest flacky

Project Member Reported by sunxd@chromium.org, Mar 3 2016

Issue description

OS: Windows

On trybot win_chromium_rel_ng and win_chromium_x64_rel_ng, the test sometimes fails due to timeout.

My run with patch fails on this test 3 times and that without patch fails twice. I also see several different CLs
fail this test on win_chromium_rel_ng. So I think this is probably a problem of the test itself.

The output of the trybot on one of my CL
(https://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_ng/builds/183638):

Retrying 1 test (retry #3)
Still waiting for the following processes to finish:
	"..\..\out\Release\views_unittests.exe" --brave-new-test-launcher --gtest_flagfile="C:\Users\chrome-bot\AppData\Local\Temp\scoped_dir600_11854\3F0.tmp" --single-process-tests --test-launcher-bot-mode --test-launcher-output="C:\Users\CHROME~2\AppData\Local\Temp\600_2669\test_results.xml" --test-launcher-summary-output="e:\b\swarm_slave\work\isolated\outwos4nk\output.json"
Still waiting for the following processes to finish:
	"..\..\out\Release\views_unittests.exe" --brave-new-test-launcher --gtest_flagfile="C:\Users\chrome-bot\AppData\Local\Temp\scoped_dir600_11854\3F0.tmp" --single-process-tests --test-launcher-bot-mode --test-launcher-output="C:\Users\CHROME~2\AppData\Local\Temp\600_2669\test_results.xml" --test-launcher-summary-output="e:\b\swarm_slave\work\isolated\outwos4nk\output.json"
Still waiting for the following processes to finish:
	"..\..\out\Release\views_unittests.exe" --brave-new-test-launcher --gtest_flagfile="C:\Users\chrome-bot\AppData\Local\Temp\scoped_dir600_11854\3F0.tmp" --single-process-tests --test-launcher-bot-mode --test-launcher-output="C:\Users\CHROME~2\AppData\Local\Temp\600_2669\test_results.xml" --test-launcher-summary-output="e:\b\swarm_slave\work\isolated\outwos4nk\output.json"
[ RUN      ] WidgetTest.SysCommandMoveOnNCLButtonDownOnCaptionAndMoveTest

[692/692] WidgetTest.SysCommandMoveOnNCLButtonDownOnCaptionAndMoveTest (TIMED OUT)
1 test timed out:
    WidgetTest.SysCommandMoveOnNCLButtonDownOnCaptionAndMoveTest (e:\b\build\slave\win\build\src\ui\views\widget\widget_unittest.cc:3273)
 
Labels: Te-NeedsFurtherTriage
Project Member

Comment 2 by sheriffbot@chromium.org, Mar 6 2017

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 3 by sunxd@chromium.org, Mar 6 2017

Status: WontFix (was: Archived)
The flacky test occurs no more, so I'll close this bug.

Sign in to add a comment