Issue metadata
Sign in to add a comment
|
"__main__.MobileEmulationCapabilityTest.testNetworkConnectionUnsupported" is flaky |
||||||||||||||||||||||||
Issue description"__main__.MobileEmulationCapabilityTest.testNetworkConnectionUnsupported" is flaky. This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is infrastructure-related, please add Infra-Troopers label and change issue status to Untriaged. When done, please remove the issue from Sheriff Bug Queue by removing the Sheriff-Chromium label. We have detected 3 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyUgsSBUZsYWtlIkdfX21haW5fXy5Nb2JpbGVFbXVsYXRpb25DYXBhYmlsaXR5VGVzdC50ZXN0TmV0d29ya0Nvbm5lY3Rpb25VbnN1cHBvcnRlZAw. Flaky tests should be disabled within 30 minutes unless culprit CL is found and reverted. Please see more details here: https://sites.google.com/a/chromium.org/dev/developers/tree-sheriffs/sheriffing-bug-queues#triaging-auto-filed-flakiness-bugs
,
Jul 18
This may be the same issue as 864205 +r johnchen in case it is.
,
Jul 18
It's probably the same issue as 864205, however this flake contains failures on Mac and Linux, in addition to Windows. Also, the Linux failure in https://ci.chromium.org/p/chromium/builders/luci.chromium.try/linux_chromium_rel_ng/142849 contains a stack trace of where Chrome crashed: [2144:2144:0717/154814.867678:FATAL:ref_counted.h(61)] Check failed: CalledOnValidSequence(). #0 0x55a58c196f8c base::debug::StackTrace::StackTrace() #1 0x55a58c0e505b logging::LogMessage::~LogMessage() #2 0x55a58974e617 base::subtle::RefCountedBase::AddRef() #3 0x55a58ccb2f59 network::ResourceResponseInfo::ResourceResponseInfo() #4 0x55a58d315cac network::(anonymous namespace)::SimpleURLLoaderImpl::OnReceiveResponse() #5 0x55a58983d98f network::mojom::URLLoaderClientStubDispatch::Accept() #6 0x55a58c7fa4e2 mojo::InterfaceEndpointClient::HandleValidatedMessage() #7 0x55a58c7fa066 mojo::FilterChain::Accept() #8 0x55a58c7fb9e2 mojo::InterfaceEndpointClient::HandleIncomingMessage() #9 0x55a58c802dad mojo::internal::MultiplexRouter::ProcessIncomingMessage() #10 0x55a58c802160 mojo::internal::MultiplexRouter::Accept() #11 0x55a58c7fa066 mojo::FilterChain::Accept() #12 0x55a58c7f793b mojo::Connector::ReadSingleMessage() #13 0x55a58c7f8434 mojo::Connector::ReadAllAvailableMessages() #14 0x55a58c7f8296 mojo::Connector::OnHandleReadyInternal() #15 0x55a589ee7724 mojo::SimpleWatcher::DiscardReadyState() #16 0x55a58c7eb853 mojo::SimpleWatcher::OnHandleReady() #17 0x55a58c7ebdce _ZN4base8internal7InvokerINS0_9BindStateIMN4mojo13SimpleWatcherEFvijRKNS3_18HandleSignalsStateEEJNS_7WeakPtrIS4_EEijS5_EEEFvvEE7RunImplIRKS9_RKNSt3__15tupleIJSB_ijS5_EEEJLm0ELm1ELm2ELm3EEEEvOT_OT0_NSI_16integer_sequenceImJXspT1_EEEE #18 0x55a58c0edffd base::debug::TaskAnnotator::RunTask() #19 0x55a58c0ec676 base::MessageLoop::RunTask() #20 0x55a58c0eca8a base::MessageLoop::DeferOrRunPendingTask() #21 0x55a58c0ecdbc base::MessageLoop::DoWork() #22 0x55a58c0f252f base::(anonymous namespace)::WorkSourceDispatch() #23 0x7fec27f46e04 g_main_context_dispatch #24 0x7fec27f47048 <unknown> #25 0x7fec27f470ec g_main_context_iteration #26 0x55a58c0f22e2 base::MessagePumpGlib::Run() #27 0x55a58c0ebfe1 base::MessageLoop::Run() #28 0x55a58c118686 base::RunLoop::Run() #29 0x55a58bd349e8 ChromeBrowserMainParts::MainMessageLoopRun() #30 0x55a58a1f5a97 content::BrowserMainLoop::RunMainMessageLoopParts() #31 0x55a58a1f8c13 content::BrowserMainRunnerImpl::Run() #32 0x55a58a1f1829 content::BrowserMain() #33 0x55a58bcd85d4 content::ContentMainRunnerImpl::Run() #34 0x55a58bd0ecd9 service_manager::Main() #35 0x55a58bcd6631 content::ContentMain() #36 0x55a5893d11b3 ChromeMain #37 0x7fec24182f45 __libc_start_main #38 0x55a5893d102a _start Since the top of the call stack contains network and mojo methods, I've added components Internals>Mojo and Internals>Network, so people in those teams can take a look.
,
Jul 19
Suspect this is a dupe of issue 864915 (Which is due to mojo secretly passing non-thread-safe refcounted objects between threads)
,
Jul 19
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by iclell...@chromium.org
, Jul 18Owner: kereliuk@chromium.org
Status: Assigned (was: Untriaged)