"BrowserTest.ThirtyFourTabs" is flaky |
|||||
Issue description"BrowserTest.ThirtyFourTabs" 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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyJQsSBUZsYWtlIhpCcm93c2VyVGVzdC5UaGlydHlGb3VyVGFicww. 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
,
Apr 5 2017
Sadrul: looking at https://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_chromeos_ozone_rel_ng/builds/355132, it has the following stack trace: Received signal 11 SEGV_MAPERR 0000000000f0 #0 0x0000035ece97 base::debug::StackTrace::StackTrace() #1 0x0000035eca0f base::debug::(anonymous namespace)::StackDumpSignalHandler() #2 0x7fe153554330 <unknown> #3 0x0000034ee1cf ui::GpuMain::CreateFrameSinkManagerInternal() #4 0x0000034ee083 ui::GpuMain::CreateFrameSinkManager() #5 0x0000025f5c06 ui::mojom::GpuMainStubDispatch::Accept() #6 0x0000047acb7a mojo::InterfaceEndpointClient::HandleValidatedMessage() #7 0x0000047bef36 mojo::FilterChain::Accept() #8 0x0000047adbcb mojo::InterfaceEndpointClient::HandleIncomingMessage() #9 0x0000047b43e9 mojo::internal::MultiplexRouter::ProcessIncomingMessage() #10 0x0000047b3c24 mojo::internal::MultiplexRouter::Accept() #11 0x0000047bef36 mojo::FilterChain::Accept() #12 0x0000047ab09b mojo::Connector::ReadSingleMessage() #13 0x0000047ab712 mojo::Connector::ReadAllAvailableMessages() #14 0x0000047ab5db mojo::Connector::OnHandleReadyInternal() #15 0x0000047c081c mojo::SimpleWatcher::OnHandleReady() #16 0x0000024b8345 _ZN4base8internal7InvokerINS0_9BindStateIMN7content25ServiceWorkerProviderHostEFviN5blink21WebServiceWorkerStateEEJNS_7WeakPtrIS4_EEiS6_EEEFvvEE7RunImplIRKS8_RKSt5tupleIJSA_iS6_EEJLm0ELm1ELm2EEEEvOT_OT0_NS_13IndexSequenceIJXspT1_EEEE #17 0x0000006c44b4 _ZNO4base8CallbackIFvvELNS_8internal8CopyModeE1ELNS2_10RepeatModeE1EE3RunEv #18 0x000003695123 base::debug::TaskAnnotator::RunTask() #19 0x00000360c16d base::MessageLoop::RunTask() #20 0x00000360c3f8 base::MessageLoop::DeferOrRunPendingTask() #21 0x00000360c886 base::MessageLoop::DoWork() #22 0x00000360ee39 base::MessagePumpLibevent::Run() #23 0x00000360befa base::MessageLoop::RunHandler() #24 0x00000363292f base::RunLoop::Run() #25 0x0000035df533 (anonymous namespace)::StartChildApp() #26 0x000002287664 _ZN4base8internal7InvokerINS0_9BindStateIPFvN4mojo16InterfaceRequestIN5blink5mojom20InstalledAppProviderEEEEJEEES9_E3RunEPNS0_13BindStateBaseEOS8_ #27 0x000001fc7d83 service_manager::RunStandaloneService() #28 0x0000035df226 RunMashBrowserTests() #29 0x0000035df0b3 main #30 0x7fe14fbcff45 __libc_start_main #31 0x0000006192ed <unknown> r8: 000000000000ffff r9: 0000000000000000 r10: 00007fe14fcee290 r11: 0000000000000246 r12: 00001e90a3431e00 r13: 0000000000000000 r14: 00007ffcd128b1b0 r15: 00007ffcd128b1a0 di: 00001e90a3443d88 si: 00001e90a338b400 bp: 00001e90a338b000 bx: 00007ffcd128b1b0 dx: 00001e90a338b400 ax: 00001e90a350db80 cx: 0000000000000000 sp: 00007ffcd128af40 ip: 00000000034ee1cf efl: 0000000000010202 cgf: 0000000000000033 erf: 0000000000000004 trp: 000000000000000e msk: 0000000000000000 cr2: 00000000000000f0 [end of stack trace] Calling _exit(1). Core file will not be generated. Could it have anything to do with https://codereview.chromium.org/2781293003? Please have a look.
,
Apr 5 2017
I don't think that CL would cause this. Looks like the crash is from accessing a null-pointer? Passing on to fsamuel@
,
Apr 5 2017
,
Apr 10 2017
This is weird. https://luci-logdog.appspot.com/v/?s=chromium%2Fbb%2Ftryserver.chromium.linux%2Flinux_chromium_chromeos_ozone_rel_ng%2F356979%2F%2B%2Frecipes%2Fsteps%2Fmash_browser_tests__with_patch_%2F0%2Fstdout Looking at this failure, it seems like we crash after timeout...I wonder if that's the case with this call stack too?
,
Aug 13
It looks like this test hasn't flaked in a long time. Marking as WontFix. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by maxmorin@chromium.org
, Apr 5 2017