"gpu_tests.context_lost_integration_test.ContextLostIntegrationTest.GpuCrash_GPUProcessCrashesExactlyOncePerVisitToAboutGpuCrash" is flaky |
||||
Issue description"gpu_tests.context_lost_integration_test.ContextLostIntegrationTest.GpuCrash_GPUProcessCrashesExactlyOncePerVisitToAboutGpuCrash" 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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyigELEgVGbGFrZSJ_Z3B1X3Rlc3RzLmNvbnRleHRfbG9zdF9pbnRlZ3JhdGlvbl90ZXN0LkNvbnRleHRMb3N0SW50ZWdyYXRpb25UZXN0LkdwdUNyYXNoX0dQVVByb2Nlc3NDcmFzaGVzRXhhY3RseU9uY2VQZXJWaXNpdFRvQWJvdXRHcHVDcmFzaAw. 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
,
Mar 21 2018
Kenneth, can you please take a look?
,
Mar 26 2018
This hasn't failed in the last 200 builds.
,
Mar 29 2018
Sorry I didn't get to this. This was caused a crash in Viz which must have been fixed elsewhere. https://ci.chromium.org/buildbot/tryserver.chromium.win/win7_chromium_rel_ng/124809 https://chromium-swarm.appspot.com/task?id=3c4d6e2055a70210&refresh=10&show_raw=1 ChildEBP RetAddr Args to Child 00eedf1c 6e1f19bf 701bd4db 00000291 0ffbdfb2 chrome!base::debug::BreakDebugger+0xc 00eedf3c 6e11d97d 0568b580 701bd4db 00000291 chrome!?Run@?$Invoker@U?$BindState@P6AXPBDHV?$BasicStringPiece@V?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@base@@1@Z$$V@internal@base@@$$A6AXPBDHV?$BasicStringPiece@V?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@3@1@Z@internal@base@@SAXPAVBindStateBase@23@PBDH$$QAV?$BasicStringPiece@V?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@3@2@Z+0x1f 00eee470 6ec23c20 00000000 00000055 00000404 chrome!logging::LogMessage::~LogMessage+0x46d 00eee550 6ec22f2e 00eee5f0 0c2b2280 000000b3 chrome!viz::DirectRenderer::ComputeScissorRectForRenderPass+0x140 00eee6c8 6ec22618 0c2b2280 6ec21f81 0c4b7c98 chrome!viz::DirectRenderer::DrawRenderPass+0x23e 00eee6f4 6ec21fa0 0c2b2280 0fefa1c8 0c4b7c98 chrome!viz::DirectRenderer::DrawRenderPassAndExecuteCopyRequests+0xd8 00eee89c 6ebfa7a5 00eee9dc 3f800000 0c499010 chrome!viz::DirectRenderer::DrawFrame+0xc30 00eeead8 6ebf6911 30fa182d 00000000 30fa182d chrome!viz::Display::DrawAndSwap+0x695 00eeebc8 6ebf5eda 6e14fe86 00001510 00001510 chrome!viz::DisplayScheduler::DrawAndSwap+0xd1 00eeec98 6ebf58ce 6e149b83 00000000 30fa1e6d chrome!viz::DisplayScheduler::AttemptDrawAndSwap+0xea 00eeed88 6ebf07b4 00eeee5c 6ebf5850 00eeee64 chrome!viz::DisplayScheduler::OnBeginFrameDeadline+0x7e 00eeee5c 6d722a94 0c3d4de0 057e734c 00eeef80 chrome!base::internal::Invoker<base::internal::BindState<void (__thiscall viz::DisplayScheduler::*)(void),base::WeakPtr<viz::DisplayScheduler> >,void __cdecl(void)>::Run+0x94 00eeee6c 6e1df0cd 0c471d30 6e14fd57 00001510 chrome!??$ForwardRepeating@$$V@?$CancelableCallbackImpl@V?$RepeatingCallback@$$A6AXXZ@base@@@internal@base@@AAEXXZ+0x10 00eeef80 6e1caf89 6ff4e147 00eef260 00eeefb8 chrome!base::debug::TaskAnnotator::RunTask+0xed 00eef054 6e164717 00eef260 057e7268 701bb3af chrome!base::internal::IncomingTaskQueue::RunTask+0x69 00eef17c 6e164a7d 00eef260 00eef1b0 6e162eed chrome!base::MessageLoop::RunTask+0x207 00eef258 6e164f12 00000000 701bb5c4 701bb3af chrome!base::MessageLoop::DeferOrRunPendingTask+0x9d 00eef3ac 6e17cd0d 057e3d80 057e3d80 000b019a chrome!base::MessageLoop::DoDelayedWork+0x232 00eef3e8 6e17c85e 057e7268 057e7200 00000001 chrome!base::MessagePumpForUI::DoRunLoop+0x8d 00eef41c 6e1640b9 057e7268 00000000 057e7268 chrome!base::MessagePumpWin::Run+0x6e 00eef4f4 6e147c2c 00000001 00eef5e0 6e0da792 chrome!base::MessageLoop::Run+0xa9 00eef5c8 6e0c3d4a 6e121bb6 6e121c57 00000000 chrome!base::RunLoop::Run+0xcc 00eef6a4 6d9ddbfd 0568d650 30fa0411 00eef6f0 chrome!ChromeBrowserMainParts::MainMessageLoopRun+0xd8 00eef6d8 6d9e02c2 00eef6f0 00eef720 6d9e0700 chrome!content::BrowserMainLoop::RunMainMessageLoopParts+0x3b 00eef7a0 6d9db0a5 00eef7b8 6e119a10 30fa0511 chrome!content::BrowserMainRunnerImpl::Run+0x8e 00eef7e4 6e02732e 00eef8d4 6e1b56ae 05680000 chrome!content::BrowserMain+0x9d 00eef8b4 6e02785f 00eef8e8 00eef8d4 00eefb34 chrome!content::RunNamedProcessTypeMain+0xee 00eef9b0 6e0400e9 00000000 00000003 00eefad0 chrome!content::ContentMainRunnerImpl::Run+0x117 00eefac0 6e027217 00eefacc 00eefad0 6ff0fff0 chrome!service_manager::Main+0x2a5 00eefafc 6d34119a 00eefb20 00eefb08 00eefb04 chrome!content::ContentMain+0x33 *** WARNING: Unable to verify checksum for chrome.exe 00eefb68 00f453ba 00f40000 00eefbb0 33855363 chrome!ChromeMain+0x11e 00eefbf4 00f41543 00f40000 33855363 00000006 chrome_exe!MainDllLoader::Launch+0x230 00eefd70 010244e8 00f40000 00000000 056b2720 chrome_exe!wWinMain+0x543 |
||||
►
Sign in to add a comment |
||||
Comment 1 by chromium...@appspot.gserviceaccount.com
, Mar 20 2018