Issue metadata
Sign in to add a comment
|
headless_browsertests failing on chromium.win/Win10 Tests x64 (dbg) |
||||||||||||||||||||||||
Issue descriptionFiled by sheriff-o-matic@appspot.gserviceaccount.com on behalf of nednguyen@google.com headless_browsertests failing on chromium.win/Win10 Tests x64 (dbg) Builders failed on: - Win10 Tests x64 (dbg): https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Win10%20Tests%20x64%20%28dbg%29
,
Nov 28
Looks like the renderer process is crashing in most (all?) tests: ../../headless/test/headless_browser_test.cc(266): error: Failed Abnormal renderer termination Stack trace: Backtrace: StackTraceGetter::CurrentStackTrace [0x00007FF6A84F29F0+80] testing::internal::UnitTestImpl::CurrentOsStackTraceExceptTop [0x00007FF6A8509E3A+90] testing::internal::AssertHelper::operator= [0x00007FF6A850991A+90] headless::HeadlessAsyncDevTooledBrowserTest::RenderProcessExited [0x00007FF6A7F9F8C0+192] headless::HeadlessWebContentsImpl::RenderProcessExited [0x00007FFC8900633E+414] content::RenderProcessHostImpl::ProcessDied [0x00007FFC7D649474+1236] content::RenderProcessHostImpl::OnChannelError [0x00007FFC7D64B2F3+179] IPC::ChannelProxy::Context::OnDispatchError [0x00007FFC92A3C47D+45] The log doesn't appear to contain the crash reason :\ However the latest runs on the bots are green now.
,
Nov 29
ping? Tests are still flaky: https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Win10%20Tests%20x64%20%28dbg%29/4550
,
Dec 3
,
Dec 12
Still flaky as of today. The rate of flakiness is quite high: https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=headless_browsertests&tests=Headless Could someone please take a look? (With all the experimental tests failing every single run on this bot, additional flakies like these distract a lot from other severe problems)
,
Dec 14
Merge this into bug 876224?
,
Dec 14
I am not sure why this still shows up on SoM even after the sheriff label is gone.
,
Dec 15
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/7e42384992ccc9874365ba5f28ae389d527d1401 commit 7e42384992ccc9874365ba5f28ae389d527d1401 Author: Andrey Kosyakov <caseq@chromium.org> Date: Sat Dec 15 02:50:23 2018 Fix a race in headless virtual time & compositor tests A lack of explicit start time for frame caused real time clock to be used for frame start, which may cause next frame to be dropped if its (virtual) timestamp is earlier. Bug: 909043 , 843734 Change-Id: I4a909be2e1e4f69f0834a87ffdb3d402c450adfc Reviewed-on: https://chromium-review.googlesource.com/c/1379181 Commit-Queue: Andrey Kosyakov <caseq@chromium.org> Reviewed-by: Pavel Feldman <pfeldman@chromium.org> Cr-Commit-Position: refs/heads/master@{#616925} [modify] https://crrev.com/7e42384992ccc9874365ba5f28ae389d527d1401/headless/test/data/protocol/emulation/compositor-image-animation-test.js [modify] https://crrev.com/7e42384992ccc9874365ba5f28ae389d527d1401/headless/test/data/protocol/helpers/virtual-time-controller.js
,
Dec 15
,
Dec 27
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by nedngu...@google.com
, Nov 28Owner: skyos...@chromium.org