New issue
Advanced search Search tips

Issue 785610 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: ----
Type: ----



Sign in to add a comment

virtual/.../inline-with-empty-inline-children.html in webkit_layout_tests failing on multiple builders

Project Member Reported by horo@chromium.org, Nov 16 2017

Issue description

virtual/.../inline-with-empty-inline-children.html in webkit_layout_tests failing on multiple builders

Builders failed on: 
- Linux Tests: 
  https://build.chromium.org/p/chromium.linux/builders/Linux%20Tests
- Mac10.10 Tests: 
  https://build.chromium.org/p/chromium.mac/builders/Mac10.10%20Tests
- Mac10.11 Tests: 
  https://build.chromium.org/p/chromium.mac/builders/Mac10.11%20Tests
- WebKit Win7: 
  https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Win7



 

Comment 1 by horo@chromium.org, Nov 16 2017

Owner: mstensho@chromium.org
Status: Assigned (was: Available)
Project Member

Comment 2 by bugdroid1@chromium.org, Nov 16 2017

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

commit 5636ee11d50f14c9846f9b11c6d01bad969bf71f
Author: Tsuyoshi Horo <horo@chromium.org>
Date: Thu Nov 16 02:17:15 2017

Mark inline-with-empty-inline-children.html as Failure

TBR: mstensho@chromium.org
Bug:  714962 , 785610 
Change-Id: I51fafd6258eb659a61688dd7ffe228966205685c
Reviewed-on: https://chromium-review.googlesource.com/773918
Reviewed-by: Tsuyoshi Horo <horo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516958}
[modify] https://crrev.com/5636ee11d50f14c9846f9b11c6d01bad969bf71f/third_party/WebKit/LayoutTests/TestExpectations

That test still crashes here. It used to be expected to crash, but as of 5636ee11d50f14c9846f9b11c6d01bad969bf71f (the above CL), it's expected to fail (without crashing). Is it flaky, or what? I get it to crash every time.

STDERR: [1:1:1116/145011.641758:FATAL:ContainerNode.cpp(1022)] Check failed: CanUseInlineBox(*o). 
STDERR: #0 0x7fb171a30ecd base::debug::StackTrace::StackTrace()
STDERR: #1 0x7fb171a2f2fc base::debug::StackTrace::StackTrace()
STDERR: #2 0x7fb171ab6d3a logging::LogMessage::~LogMessage()
STDERR: #3 0x7fb1697f0979 blink::ContainerNode::GetUpperLeftCorner()
STDERR: #4 0x7fb1697f1499 blink::ContainerNode::BoundingBox()
STDERR: #5 0x7fb16987979d blink::Element::scrollIntoViewWithOptions()
STDERR: #6 0x7fb169879685 blink::Element::scrollIntoView()
STDERR: #7 0x7fb169879853 blink::Element::scrollIntoView()
STDERR: #8 0x7fb16aa50c05 blink::ElementV8Internal::scrollIntoViewMethod()
STDERR: #9 0x7fb16aa5095a blink::V8Element::scrollIntoViewMethodCallback()
STDERR: #10 0x7fb16b86c0d2 v8::internal::FunctionCallbackArguments::Call()
STDERR: #11 0x7fb16b96673b v8::internal::(anonymous namespace)::HandleApiCallHelper<>()
STDERR: #12 0x7fb16b9648e3 v8::internal::Builtin_Impl_HandleApiCall()
STDERR: #13 0x7fb16b9642ad v8::internal::Builtin_HandleApiCall()

Comment 4 by guidou@chromium.org, Nov 16 2017

Labels: -Sheriff-Chromium
Project Member

Comment 5 by bugdroid1@chromium.org, Nov 16 2017

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

commit a1a1d82e8534172b7b27628adb37161479a6c530
Author: Guido Urdaneta <guidou@chromium.org>
Date: Thu Nov 16 16:36:35 2017

Update expectation for virtual/.../inline-with-empty-inline-children.html

The test crashes flakily on various bots.
Sample runs:
https://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%28dbg%29%281%29/builds/64670
https://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%28dbg%29%281%29/builds/64668

TBR=mstensho@chromium.org

Bug:  785610 
Change-Id: I3e344e9d361bbfa1b1f31257c75d88bd222021fa
Reviewed-on: https://chromium-review.googlesource.com/774886
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Commit-Queue: Guido Urdaneta <guidou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517106}
[modify] https://crrev.com/a1a1d82e8534172b7b27628adb37161479a6c530/third_party/WebKit/LayoutTests/TestExpectations

Status: WontFix (was: Assigned)
Probably no need to keep a separate report for this. Lots of things that don't work in NG. :)

Sign in to add a comment