Issue metadata
Sign in to add a comment
|
telemetry_unittests failing on chromium.win/Win7 Tests (dbg)(1) |
||||||||||||||||||
Issue descriptiontelemetry_unittests failing on chromium.win/Win7 Tests (dbg)(1) Builders failed on: - Win7 Tests (dbg)(1): https://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%28dbg%29%281%29
,
Aug 3 2017
According to the log, GPU process is crashing. https://luci-logdog.appspot.com/v/?s=chromium%2Fbb%2Fchromium.win%2FWin7_Tests__dbg__1_%2F62028%2F%2B%2Frecipes%2Fsteps%2Ftelemetry_unittests%2F0%2Fstdout 33f7c788 1e516d65 7c5177d8 00000001 00000001 content!content::GpuProcessHost::~GpuProcessHost+0x440 33f7c7a8 1e50bf8b 00000001 00000001 30b3ba58 content!content::GpuProcessHost::`scalar deleting destructor'+0x25 33f7cac8 1e48f2d3 00000001 00000001 00000064 content!content::GpuProcessHost::Get+0x55b 33f7cc80 1e48f9c8 22511ada 07c7f4b4 07c7f4b4 content!content::BrowserGpuChannelHostFactory::EstablishRequest::EstablishOnIO+0xe3 33f7cda0 1e49478d 33f7cfb8 33f7cfc0 00000001 content!content::BrowserGpuChannelHostFactory::EstablishRequest::OnEstablishedOnIO+0x168 33f7cde0 1e4946b1 1bd1ac7f 358295d0 33f7cfb8 content!base::internal::FunctorTraits<void (__thiscall content::BrowserGpuChannelHostFactory::EstablishRequest::*)(IPC::ChannelHandle const &,gpu::GPUInfo const &,enum content::GpuProcessHost::EstablishChannelStatus),void>::Invoke<scoped_refptr<content::BrowserGpuChannelHostFactory::EstablishRequest> const &,IPC::ChannelHandle const &,gpu::GPUInfo const &,enum content::GpuProcessHost::EstablishChannelStatus>+0x7d 33f7ce34 1e4945be 358295cc 358295d0 33f7cfb8 content!base::internal::InvokeHelper<0,void>::MakeItSo<void (__thiscall content::BrowserGpuChannelHostFactory::EstablishRequest::*const &)(IPC::ChannelHandle const &,gpu::GPUInfo const &,enum content::GpuProcessHost::EstablishChannelStatus),scoped_refptr<content::BrowserGpuChannelHostFactory::EstablishRequest> const &,IPC::ChannelHandle const &,gpu::GPUInfo const &,enum content::GpuProcessHost::EstablishChannelStatus>+0xa1 33f7ce80 1e4943ea 358295cc 358295d0 33f7d2bc content!base::internal::Invoker<base::internal::BindState<void (__thiscall content::BrowserGpuChannelHostFactory::EstablishRequest::*)(IPC::ChannelHandle const &,gpu::GPUInfo const &,enum content::GpuProcessHost::EstablishChannelStatus),scoped_refptr<content::BrowserGpuChannelHostFactory::EstablishRequest> >,void __cdecl(IPC::ChannelHandle const &,gpu::GPUInfo const &,enum content::GpuProcessHost::EstablishChannelStatus)>::RunImpl<void (__thiscall content::BrowserGpuChannelHostFactory::EstablishRequest::*const &)(IPC::ChannelHandle const &,gpu::GPUInfo const &,enum content::GpuProcessHost::EstablishChannelStatus),std::tuple<scoped_refptr<content::BrowserGpuChannelHostFactory::EstablishRequest> > const &,0>+0x9e 33f7ced0 1e511671 358295b8 33f7cfb8 33f7cfc0 content!base::internal::Invoker<base::internal::BindState<void (__thiscall content::BrowserGpuChannelHostFactory::EstablishRequest::*)(IPC::ChannelHandle const &,gpu::GPUInfo const &,enum content::GpuProcessHost::EstablishChannelStatus),scoped_refptr<content::BrowserGpuChannelHostFactory::EstablishRequest> >,void __cdecl(IPC::ChannelHandle const &,gpu::GPUInfo const &,enum content::GpuProcessHost::EstablishChannelStatus)>::Run+0x8a 33f7cf20 1e50e721 33f7cfb8 33f7cfc0 00000001 content!base::Callback<void __cdecl(IPC::ChannelHandle const &,gpu::GPUInfo const &,enum content::GpuProcessHost::EstablishChannelStatus),1,1>::Run+0x91 33f7d238 1e513bc2 00000001 33f7d258 05f9959e content!content::GpuProcessHost::SendOutstandingReplies+0xe1 33f7d2dc 1dc4db8a 00000004 05f4456f 3581caa0 content!content::GpuProcessHost::OnProcessCrashed+0x1a2 33f7d59c 1c450c5e 00000003 2244da30 00000003 content!content::BrowserChildProcessHostImpl::OnChildDisconnected+0x2da *** WARNING: Unable to verify checksum for ipc.dll 33f7d5c0 08a1a8b4 00000001 3581caa0 3581caa0 content!content::ChildProcessHostImpl::OnChannelError+0x8e 33f7d748 08a5a07e 00000000 00000000 33f7d768 ipc!IPC::ChannelMojo::OnPipeError+0x164
,
Aug 3 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/27004cb5e9005aa1bd43b0e5d8dce18bfed15193 commit 27004cb5e9005aa1bd43b0e5d8dce18bfed15193 Author: Tsuyoshi Horo <horo@chromium.org> Date: Thu Aug 03 08:04:48 2017 Revert "Roll SwiftShader 4d3efed..8aa0768" This reverts commit 293a6765dd36405b98ce9b0ccf0f313d23f81b21. Reason for revert: I think this CL caused telemetry_unittests failures. BUG:751967 Original change's description: > Roll SwiftShader 4d3efed..8aa0768 > > https://swiftshader.googlesource.com/SwiftShader.git/+log/4d3efed..8aa0768 > > BUG= > > TBR=kbr@chromium.org > > TEST=bots > > CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel,linux_chromium_cfi_rel_ng;master.tryserver.chromium.android:android_optional_gpu_tests_rel > > Change-Id: I1f88e9213f4387e38b4b9d1059d7ee9a419d755f > Reviewed-on: https://chromium-review.googlesource.com/599015 > Reviewed-by: Alexis Hétu <sugoi@chromium.org> > Commit-Queue: Alexis Hétu <sugoi@chromium.org> > Cr-Commit-Position: refs/heads/master@{#491572} TBR=sugoi@chromium.org,kbr@chromium.org Change-Id: If0463d4bc1a2036feb1317a04c910dc33891755a No-Presubmit: true No-Tree-Checks: true No-Try: true Cq-Include-Trybots: master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel, linux_chromium_cfi_rel_ng;master.tryserver.chromium.android:android_optional_gpu_tests_rel Reviewed-on: https://chromium-review.googlesource.com/599174 Reviewed-by: Tsuyoshi Horo <horo@chromium.org> Commit-Queue: Tsuyoshi Horo <horo@chromium.org> Cr-Commit-Position: refs/heads/master@{#491673} [modify] https://crrev.com/27004cb5e9005aa1bd43b0e5d8dce18bfed15193/DEPS
,
Aug 3 2017
,
Aug 8 2017
The plausible patch has been reverted and the problem looks fixed, so removed the sheriff label.
,
Aug 8
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by horo@chromium.org
, Aug 3 2017