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

Issue 636977 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jan 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

ContentBrowserTest.RendererCrashCallStack fails on win7

Project Member Reported by xidac...@chromium.org, Aug 11 2016

Issue description

Build is broken:
content_browsertests on Windows-7-SP1

Revision range:
chromium 410712 : 410732

Failing builders:
Win7 Tests (1): https://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20(1)


 
Project Member

Comment 1 by bugdroid1@chromium.org, Aug 11 2016

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

commit 1cd4e33d451c2b1ff88e3aeebe85d7dae4d979b1
Author: xidachen <xidachen@chromium.org>
Date: Thu Aug 11 15:39:00 2016

Disable ContentBrowserTest.RendererCrashCallStack on win7

TBR=lukasza@chromium.org
NOTRY=true
BUG= 636977 

Review-Url: https://codereview.chromium.org/2238963002
Cr-Commit-Position: refs/heads/master@{#411338}

[modify] https://crrev.com/1cd4e33d451c2b1ff88e3aeebe85d7dae4d979b1/content/test/content_browser_test_test.cc

Comment 2 by roc...@chromium.org, Aug 11 2016

Cc: roc...@chromium.org
 Issue 636624  has been merged into this issue.
I can't repro on a Win7, using a local build at the same commit and with the same args.gn as what was used for the first failing build - https://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%281%29/builds/55907
Cc: lukasza@chromium.org
Owner: alokp@chromium.org
xidachen@, could you help me understand why I got assigned this bug (I am not on the blamelist of the build I mention in #c3 + the test times out / there is no test output or callstack to point a finger at me).  There is one CL on the blamelist that looks related - r410730, so let me try reassigning this bug to alokp@.
lukasza@: sorry for any confusion. I am sheriffing today, and it seems that you are the owner of this test, so that's why I assigned the bug to you. Thanks for looking into this issue and re-assign to the right owner.
Let me clarify that I am not at all sure whether alokp@ is the right owner :-(  It's just that his/her CL is one of the few in the blamelist that touch //content layer... And now I see that CheckAllWorkersTerminated is no longer present in the code...  Hmmm...

I am not sure how to make progress here without a local repro.

Comment 7 by alokp@chromium.org, Aug 24 2016

Owner: ----
My patch is already reverted and does not seem related.
Project Member

Comment 8 by bugdroid1@chromium.org, Jan 4 2017

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

commit 6628b2ef2638bf6dca616d58c7f499176a650d92
Author: jam <jam@chromium.org>
Date: Wed Jan 04 19:18:55 2017

Renable ContentBrowserTest.RendererCrashCallStack

BUG= 636977 

Review-Url: https://codereview.chromium.org/2610803003
Cr-Commit-Position: refs/heads/master@{#441430}

[modify] https://crrev.com/6628b2ef2638bf6dca616d58c7f499176a650d92/content/test/content_browser_test_test.cc

Comment 9 by jam@chromium.org, Jan 5 2017

Status: WontFix (was: Available)
I've reverted the disable and no issues seen.

Sign in to add a comment