Test crash log.

[ RUN      ] LocalNTPInterceptionWebRequestAPITest.OneGoogleBarRequestsHidden
[20778:20778:0625/062814.529817:WARNING:password_store_factory.cc(250)] Using basic (unencrypted) store for password storage. See https://chromium.googlesource.com/chromium/src/+/master/docs/linux_password_storage.md for more information about password storage options.
[20778:20815:0625/062814.559903:ERROR:bus.cc(394)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
(browser_tests:20778): LIBDBUSMENU-GLIB-WARNING **: Unable to get session bus: Unknown or unsupported transport 'disabled' for address 'disabled:'
[20778:20860:0625/062814.826100:WARNING:embedded_test_server.cc(229)] Request not handled. Returning 404: /async/ddljson?async=ntp:1
[20778:20860:0625/062814.826286:WARNING:embedded_test_server.cc(229)] Request not handled. Returning 404: /async/newtab_ogb?hl=en-US&async=fixed:0
BrowserTestBase received signal: Segmentation fault. Backtrace:
#0 0x000004ec5a3c base::debug::StackTrace::StackTrace()
#1 0x00000532b795 content::(anonymous namespace)::DumpStackTraceSignalHandler()
#2 0x7f20e8e104b0 <unknown>
#3 0x00000437f801 extensions::WebRequestProxyingURLLoaderFactory::RemoveRequest()
#4 0x00000437f756 extensions::WebRequestProxyingURLLoaderFactory::InProgressRequest::OnComplete()
#5 0x000003627e5c network::mojom::URLLoaderClientStubDispatch::Accept()
#6 0x000005c374c1 mojo::internal::MultiplexRouter::ProcessIncomingMessage()
#7 0x000005c36d15 mojo::internal::MultiplexRouter::Accept()
#8 0x000005c31350 mojo::Connector::ReadSingleMessage()
#9 0x000005c31ad1 mojo::Connector::ReadAllAvailableMessages()
#10 0x00000538da4a mojo::SimpleWatcher::OnHandleReady()
#11 0x00000538dc91 mojo::SimpleWatcher::Context::Notify()
#12 0x00000538d2c0 mojo::SimpleWatcher::Context::CallNotify()
#13 0x000003a81069 mojo::edk::WatcherDispatcher::InvokeWatchCallback()
#14 0x000003a8098c mojo::edk::Watch::InvokeCallback()
#15 0x000003a7d0cd mojo::edk::RequestContext::~RequestContext()
#16 0x000003a74a1b mojo::edk::NodeChannel::OnChannelMessage()
#17 0x000003a67770 mojo::edk::Channel::OnReadComplete()
#18 0x000003a8503f mojo::edk::(anonymous namespace)::ChannelPosix::OnFileCanReadWithoutBlocking()
#19 0x000004ed6b55 base::MessagePumpLibevent::OnLibeventNotification()
#20 0x0000058bf45d event_base_loop
#21 0x000004ed6d2e base::MessagePumpLibevent::Run()
#22 0x000004e762f5 base::RunLoop::Run()
#23 0x000003cd2a14 content::BrowserProcessSubThread::IOThreadRun()
#24 0x000004e9f3bf base::Thread::ThreadMain()
#25 0x000004ed28cd base::(anonymous namespace)::ThreadFunc()
#26 0x7f20eed3a6ba start_thread
#27 0x7f20e8ee241d clone

This failure is happening at roughly 10% to 20% of runs so I'm bumping up its priority.

The first occurrence of this seems to have happened in build #882 [1] from 2018-06-14 (most recent is #1281). Curiously this started happening after a small non-sequential series of infra/purple failed runs: #881, #871 and #863.

I wonder if this could be an infra issue? Adding trooper labels so they can PTAL.


[1] https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/linux-xenial-rel/882

#4: they appear to be standard test flakes, https://bugs.chromium.org/p/chromium/issues/detail?id=795156 notwithstanding (which is why the look like infra failures in the UI). The tests did still run (and fail in non-infra fashion):

863: https://chromium-swarm.appspot.com/task?id=3e13c0a8a542bd10
871: https://chromium-swarm.appspot.com/task?id=3e1536ad03e4a610
881: https://chromium-swarm.appspot.com/task?id=3e16cf3c4c0ad110

Back to the sheriff queue. Please try to find an owner or a suspected CL.

This same test was already flagged as flaky for Windows.