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

Issue 846729 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 846313
Owner: ----
Closed: May 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: ----



Sign in to add a comment

content_shell_crash_test failing on chromium.win/Win7 Tests (1)

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, May 25 2018

Issue description

Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of lunalu@google.com

content_shell_crash_test failing on chromium.win/Win7 Tests (1)

Builders failed on: 
- Win7 Tests (1): 
  https://ci.chromium.org/buildbot/chromium.win/Win7%20Tests%20%281%29

It's been failing since https://ci.chromium.org/buildbot/chromium.win/Win7%20Tests%20%281%29/80169

The test failure is FAIL: Could not find reference to CrashIntentionally in stack.
 
Cc: jochen@chromium.org jam@chromium.org scottmg@chromium.org
jam / scottmg / jochen - this test has been failing on the waterfall for two days. Can one of you take a look and see if you have any ideas, or find someone that does?

In the meantime, I'm disabling it, because it causes false rejections in the CQ for any CL that might have retries disabled.
Labels: -Pri-2 Pri-1
Cc: sande...@chromium.org
More generally, this test runs almost nowhere (see test_suite_exceptions.pyl). 

We should either make sure it is running everywhere, or consider removing it altogether.
Project Member

Comment 5 by bugdroid1@chromium.org, May 25 2018

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

commit 0dbdf56a78cb9328378f4d3afff45baf6859712f
Author: Dirk Pranke <dpranke@chromium.org>
Date: Fri May 25 16:21:36 2018

Disable content_shell_crash_tests on Win7 Tests (1).

It is failing, for unclear reasons. Disable to unblock the
CQ until someone can make it work again.

TBR=sandersd@chromium.org
NOTRY=true

Bug:  846729 
Change-Id: I5bb455036799fbce53ae302ff5c3761d2da2a27e
Reviewed-on: https://chromium-review.googlesource.com/1072451
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Dirk Pranke <dpranke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#561902}
[modify] https://crrev.com/0dbdf56a78cb9328378f4d3afff45baf6859712f/testing/buildbot/chromium.win.json
[modify] https://crrev.com/0dbdf56a78cb9328378f4d3afff45baf6859712f/testing/buildbot/test_suite_exceptions.pyl

Cc: gab@chromium.org brucedaw...@chromium.org
See also  bug 846729  and  bug 846313  for similar issues.

It's possible the underlying issue was fixed and we should try to re-enable.
Mergedinto: 846313
Status: Duplicate (was: Available)
Project Member

Comment 8 by bugdroid1@chromium.org, Jun 29 2018

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

commit d5296cb77eccd89a3591115c694b58205203e43b
Author: Nico Weber <thakis@chromium.org>
Date: Fri Jun 29 18:56:44 2018

Enable content_shell_crash_test on many bots.

On most bots, we don't know why the test is disabled. Worst case, we'll find
out and redisable it on bots where it doesn't yet work for some reason.

On Mac 10.13 and Win 7, we do know why it's disabled, but the Win 7 bug
has been fixed, and the 10.13 bug was spurious and I have put in better
debug logging if it were to fail again, and I haven't seen any failures in
the last 200 builds on the main waterfall.

Bug:  846729 ,813163,843511
Change-Id: Ibd14dea1c5fb72bc4d298b53f55e87be05aa211e
Reviewed-on: https://chromium-review.googlesource.com/1120225
Commit-Queue: Nico Weber <thakis@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#571572}
[modify] https://crrev.com/d5296cb77eccd89a3591115c694b58205203e43b/testing/buildbot/chromium.fyi.json
[modify] https://crrev.com/d5296cb77eccd89a3591115c694b58205203e43b/testing/buildbot/chromium.linux.json
[modify] https://crrev.com/d5296cb77eccd89a3591115c694b58205203e43b/testing/buildbot/chromium.mac.json
[modify] https://crrev.com/d5296cb77eccd89a3591115c694b58205203e43b/testing/buildbot/chromium.win.json
[modify] https://crrev.com/d5296cb77eccd89a3591115c694b58205203e43b/testing/buildbot/client.v8.chromium.json
[modify] https://crrev.com/d5296cb77eccd89a3591115c694b58205203e43b/testing/buildbot/test_suite_exceptions.pyl

Sign in to add a comment