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

Issue 606485 link

Starred by 1 user
Status: Assigned
Owner:
█ nasko@chromium.org
Out until 24 Jan
Cc:
creis@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

"ChromeRenderProcessHostTest.CloseAllTabsDuringProcessDied" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Apr 25 2016 
"ChromeRenderProcessHostTest.CloseAllTabsDuringProcessDied" is flaky.

This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is infrastructure-related, please add Infra-Troopers label and change issue status to Untriaged. When done, please remove the issue from Sheriff Bug Queue by removing the Sheriff-Chromium label.

We have detected 3 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyRAsSBUZsYWtlIjlDaHJvbWVSZW5kZXJQcm9jZXNzSG9zdFRlc3QuQ2xvc2VBbGxUYWJzRHVyaW5nUHJvY2Vzc0RpZWQM.

Flaky tests should be disabled within 30 minutes unless culprit CL is found and reverted. Please see more details here: https://sites.google.com/a/chromium.org/dev/developers/tree-sheriffs/sheriffing-bug-queues#triaging-auto-filed-flakiness-bugs

Comment 1 by creis@chromium.org, Apr 25 2016

Components: UI>Browser>Navigation
Owner: nasko@chromium.org
Nasko, can you take a look?  You added this test in ...


It does look like there's a lot of failures, as sampled below:

try run at 2016-04-25 20:09:27 UTC	patchset	win_chromium_x64_rel_ng	(reported in 606485)
try run at 2016-04-25 19:09:20 UTC	patchset	win_chromium_x64_rel_ng	(reported in 606485)
try run at 2016-04-25 19:09:20 UTC	patchset	win_chromium_x64_rel_ng	(reported in 606485)
try run at 2016-04-23 03:50:02 UTC	patchset	win_chromium_x64_rel_ng	
try run at 2016-04-23 01:46:06 UTC	patchset	win_chromium_x64_rel_ng	
 
try run at 2015-03-25 05:52:03 UTC	patchset	win_chromium_rel_ng	
try run at 2015-03-25 05:35:31 UTC	patchset	win_chromium_x64_rel_ng	
try run at 2015-03-25 05:34:08 UTC	patchset	win_chromium_x64_rel_ng	
try run at 2015-03-25 05:25:19 UTC	patchset	win_chromium_x64_rel_ng	
try run at 2015-03-25 05:23:12 UTC	patchset	win_chromium_rel_ng	
try run at 2015-03-25 05:23:12 UTC	patchset	win_chromium_rel_ng	
try run at 2015-03-25 05:09:14 UTC	patchset	win_chromium_rel_ng	
try run at 2015-03-25 05:07:48 UTC	patchset	win_chromium_x64_rel_ng	
try run at 2015-03-25 05:05:42 UTC	patchset	linux_chromium_rel_ng	
try run at 2015-03-25 05:05:42 UTC	patchset	linux_chromium_rel_ng	


ChromeRenderProcessHostTest.CloseAllTabsDuringProcessDied (run #1):
[ RUN      ] ChromeRenderProcessHostTest.CloseAllTabsDuringProcessDied
Backtrace:
	InitializeBase [0x0000000142479CF5+3576461]
	InitializeBase [0x000000014247CAB4+3588172]
	InitializeBase [0x000000014342A6AF+20028487]
	InitializeBase [0x0000000142CA146D+12126725]
	InitializeBase [0x0000000142C680E4+11892348]
	InitializeBase [0x0000000142C6809A+11892274]
	InitializeBase [0x0000000142C1AE19+11576241]
	ovly_debug_event [0x0000000144B32D59+17972313]
	ovly_debug_event [0x0000000144B32BDD+17971933]
	ovly_debug_event [0x0000000144B329DE+17971422]
	InitializeBase [0x0000000142E734B0+14035528]
	ovly_debug_event [0x0000000144B32AA7+17971623]
	ovly_debug_event [0x0000000144B3188C+17966988]
	ovly_debug_event [0x0000000144B552F5+18113013]
	InitializeBase [0x0000000142BC4798+11222320]
	InitializeBase [0x000000014343E4CD+20109925]
	InitializeBase [0x0000000142EB18FE+14290582]
	InitializeBase [0x00000001430A2FD8+16328048]
	InitializeBase [0x000000014307C318+16169136]
	InitializeBase [0x000000014307B779+16166161]
	InitializeBase [0x000000014307E519+16177841]
	InitializeBase [0x000000014307EC42+16179674]
	InitializeBase [0x000000014307F07A+16180754]
	InitializeBase [0x0000000143089B48+16224480]
	InitializeBase [0x00000001424346D7+3292271]
	ovly_debug_event [0x0000000144A3478A+16930442]
	ovly_debug_event [0x0000000144A87C65+17271653]
	GetHandleVerifier [0x00000001450F798C+275244]
	ovly_debug_event [0x0000000144A644CD+17126349]
	ovly_debug_event [0x0000000144A63948+17123400]
	ovly_debug_event [0x0000000144A2037B+16847483]
	ovly_debug_event [0x0000000144A6496E+17127534]
	GetHandleVerifier [0x00000001450F798C+275244]
	SetCrashKeyValueImpl [0x000000014506907C+2995888]
	SetCrashKeyValueImpl [0x0000000145068220+2992212]
	GetHandleVerifier [0x00000001450FCFB8+297304]
	SetCrashKeyValueImpl [0x0000000145070B7E+3027378]
	SetCrashKeyValueImpl [0x0000000145068C1B+2994767]
	ovly_debug_event [0x0000000144B8173D+18294333]
	SetCrashKeyValueImpl [0x0000000144DB5BE9+164381]
	SetCrashKeyValueImpl [0x0000000144DB5A9C+164048]
	SetCrashKeyValueImpl [0x0000000144DB4E34+160872]
	SetCrashKeyValueImpl [0x0000000144DF949F+441043]
	ScaleYUVToRGB32Row_SSE2_X64 [0x000000013FCF4AEB+1781979]
	IsSandboxedProcess [0x0000000145A8934C+5712432]
	BaseThreadInitThunk [0x0000000076C659ED+13]
	RtlUserThreadStart [0x0000000076E9C541+33]

Comment 2 by creis@chromium.org, Apr 25 2016

Cc: creis@chromium.org
Oops, forgot the link to the original CL:
https://codereview.chromium.org/18167004/

Comment 3 by creis@chromium.org, Apr 25 2016

Labels: -Sheriff-Chromium
Disabling on Windows and Mac in https://codereview.chromium.org/1921063003/.
Project Member

Comment 4 by bugdroid1@chromium.org, Apr 25 2016 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/a862383244ce0a80529eb9e3447c2d4ab43b1203

commit a862383244ce0a80529eb9e3447c2d4ab43b1203
Author: creis <creis@chromium.org>
Date: Mon Apr 25 23:54:10 2016

Disable flaky CloseAllTabsDuringProcessDied test on Win/Linux.

Test is old (https://codereview.chromium.org/18167004/) but is flaky now.

TBR=nasko,jochen
BUG=606485
TEST=Bots stay green

Review URL: https://codereview.chromium.org/1921063003

Cr-Commit-Position: refs/heads/master@{#389621}

[modify] https://crrev.com/a862383244ce0a80529eb9e3447c2d4ab43b1203/chrome/browser/renderer_host/render_process_host_chrome_browsertest.cc

Comment 5 by benhenry@chromium.org, Aug 1

Status: Assigned (was: Untriaged)
►

Sign in to add a comment