ContentBrowserTest.RendererCrashCallStack fails on win7 |
||||
Issue descriptionBuild 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)
,
Aug 11 2016
,
Aug 11 2016
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
,
Aug 11 2016
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@.
,
Aug 11 2016
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.
,
Aug 12 2016
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.
,
Aug 24 2016
My patch is already reverted and does not seem related.
,
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
,
Jan 5 2017
I've reverted the disable and no issues seen. |
||||
►
Sign in to add a comment |
||||
Comment 1 by bugdroid1@chromium.org
, Aug 11 2016