Commit c7351898 authored by Mike West's avatar Mike West Committed by Commit Bot

Disable `ShelfLayoutManagerWindowDraggingTest.NoOpForHiddenShelf`.

It looks like https://chromium-review.googlesource.com/c/chromium/src/+/1895922 causes consistent failures in `ShelfLayoutManagerWindowDraggingTest.NoOpForHiddenShelf` with the following stack:

```
Received signal 11 <unknown> 000000000000
  r8: 00002040963d13a8  r9: 00007ffdd58dcf50 r10: 0000000000000000 r11: 00007f6d6e486f90
 r12: 000055ac8516d870 r13: 00007ffdd58e0a70 r14: 0000000000000000 r15: 0000000000000000
  di: 00002040982e9db8  si: cdcdcdcdcdcdcded  bp: 00007ffdd58dd5a0  bx: 0000000000000000
  dx: 00007ffdd58dd800  ax: cdcdcdcdcdcdcded  cx: cdcdcdcdcdcdcded  sp: 00007ffdd58dd5a0
  ip: 00007f6d818945a4 efl: 0000000000010286 cgf: 002b000000000033 erf: 0000000000000000
 trp: 000000000000000d msk: 0000000000000000 cr2: 0000000000000000
```

(See https://logs.chromium.org/logs/chromium/buildbucket/cr-buildbucket.appspot.com/8896938459425026880/+/steps/ash_unittests/0/logs/Deterministic_failure:_ShelfLayoutManagerWindowDraggingTest.NoOpForHiddenShelf__status_CRASH_/0)

TBR=newcomer@chromium.org

Bug: 1024163
Change-Id: I83d55f2c1cfadcd1752b2be91d0c3d1dde1278b7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1913402Reviewed-by: default avatarMike West <mkwst@chromium.org>
Commit-Queue: Mike West <mkwst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#714871}
parent 0f3f36a7
......@@ -4420,7 +4420,8 @@ TEST_F(ShelfLayoutManagerWindowDraggingTest, NoOpInOverview) {
// Test that if shelf if hidden or auto-hide hidden, drag window from shelf is a
// no-op.
TEST_F(ShelfLayoutManagerWindowDraggingTest, NoOpForHiddenShelf) {
// TODO(1024163): This test consistently crashes.
TEST_F(ShelfLayoutManagerWindowDraggingTest, DISABLED_NoOpForHiddenShelf) {
std::unique_ptr<aura::Window> window =
AshTestBase::CreateTestWindow(gfx::Rect(0, 0, 400, 400));
wm::ActivateWindow(window.get());
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment