WebGL 2.0 tests (usually video related) flaky on Windows with Intel GPUs |
||||||||||
Issue descriptionhttps://build.chromium.org/p/chromium.gpu.fyi/builders/Win7%20Release%20%28New%20Intel%29/builds/1131 is one example of a failure of this test. Log excerpt: WebglConformance_conformance2_textures_video_tex_2d_rgb9_e5_rgb_half_float (gpu_tests.webgl_conformance_integration_test.WebGLConformanceIntegrationTest) ... [1536:2336:0714/093700:WARNING:webmediaplayer_impl.cc(335)] Using MultibufferDataSource [3580:3088:0714/093700:ERROR:audio_manager_win.cc(464)] GetPreferredAudioParameters failed: 88890004 [3572:1652:0714/093700:INFO:gpu_video_decode_accelerator_factory_impl.cc(163)] Initializing DXVA HW decoder for windows. [3580:3088:0714/093700:ERROR:audio_manager_win.cc(464)] GetPreferredAudioParameters failed: 88890004 [3580:3088:0714/093700:ERROR:audio_output_resampler.cc(240)] Unable to open audio device in low latency mode. Falling back to high latency audio output. [3580:3088:0714/093700:ERROR:audio_output_resampler.cc(250)] Unable to open audio device in high latency mode. Falling back to fake audio output. [3572:1652:0714/093700:ERROR:dxva_video_decode_accelerator_win.cc(452)] The eglQueryDeviceAttribEXT function failed to get the device [3572:1652:0714/093700:ERROR:dxva_video_decode_accelerator_win.cc(222)] Error in dxva_video_decode_accelerator_win.cc on line 452 [1536:2336:0714/093700:WARNING:webmediaplayer_impl.cc(335)] Using MultibufferDataSource [3572:1652:0714/093700:INFO:gpu_video_decode_accelerator_factory_impl.cc(163)] Initializing DXVA HW decoder for windows. [3572:1652:0714/093700:ERROR:dxva_video_decode_accelerator_win.cc(1465)] Unsupported codec. [3572:1652:0714/093700:ERROR:dxva_video_decode_accelerator_win.cc(222)] Error in dxva_video_decode_accelerator_win.cc on line 1465 [3572:1652:0714/093700:ERROR:dxva_video_decode_accelerator_win.cc(222)] Error in dxva_video_decode_accelerator_win.cc on line 709 [3572:1652:0714/093700:ERROR:gpu_video_decode_accelerator.cc(365)] HW video decode not available for profile 11 [1536:3740:0714/093700:ERROR:gpu_video_decode_accelerator_host.cc(93)] Send(GpuCommandBufferMsg_CreateVideoDecoder()) failed [1536:3740:0714/093700:ERROR:gpu_video_decoder.cc(801)] VDA Error: 4 [3572:1868:0714/093700:ERROR:gpu_channel.cc(569)] Could not find message queue [1536:3740:0714/093700:ERROR:ffmpeg_demuxer.cc(1595)] media::FFmpegDemuxer::OnReadFrameDone result=-541478725 IsMaxMemoryUsageReached=0 err: rx::SwapChain11::present(826): Present failed: the D3D11 device was removed: 0x887A0006 [3572:1652:0714/093704:ERROR:gles2_cmd_decoder.cc(13747)] Context lost because SwapBuffers failed. [3572:1652:0714/093704:ERROR:gles2_cmd_decoder.cc(14105)] Onscreen context lost via ARB/EXT_robustness. Reset status = GL_UNKNOWN_CONTEXT_RESET_KHR [3572:1652:0714/093704:ERROR:gles2_cmd_decoder.cc(5040)] Error: 5 for Command kPostSubBufferCHROMIUM [3572:1652:0714/093704:ERROR:gpu_channel_manager.cc(222)] Exiting GPU process because some drivers cannot recover from problems. Probably specific to this GPU type and texture format.
,
Jul 14 2016
Per analysis by ynovikov@ in https://bugs.chromium.org/p/chromium/issues/detail?id=624853#c27 , it looks like multiple video-related tests are flaky on this machine and it's because of DXVA video acceleration failing to initialize. Here are multiple failing builds: https://build.chromium.org/p/chromium.gpu.fyi/builders/Win7%20Release%20%28New%20Intel%29/builds/1130 WebglConformance_conformance2_textures_video_tex_2d_rgb5_a1_rgba_unsigned_byte WebglConformance_conformance2_textures_video_tex_2d_rgb9_e5_rgb_half_float WebglConformance_conformance2_textures_video_tex_2d_rgba32f_rgba_float https://build.chromium.org/p/chromium.gpu.fyi/builders/Win7%20Release%20%28New%20Intel%29/builds/1131 WebglConformance_conformance2_textures_video_tex_2d_rgb9_e5_rgb_half_float https://build.chromium.org/p/chromium.gpu.fyi/builders/Win7%20Release%20%28New%20Intel%29/builds/1132 WebglConformance_conformance2_textures_video_tex_2d_rg32f_rg_float WebglConformance_conformance2_textures_video_tex_2d_rgb5_a1_rgba_unsigned_byte WebglConformance_conformance2_textures_video_tex_2d_rgba32f_rgba_float The failures are apparently unrelated to the failure to initialize GPU-accelerated video decoding. That happens in all of the tests. The problem is that the D3D11 device spontaneously gets lost, which takes down the GPU process, causing a lost context and failing the test: err: rx::SwapChain11::present(826): Present failed: the D3D11 device was removed: 0x887A0006 [2872:3904:0714/060646:ERROR:gles2_cmd_decoder.cc(13747)] Context lost because SwapBuffers failed. [2872:3904:0714/060646:ERROR:gles2_cmd_decoder.cc(14105)] Onscreen context lost via ARB/EXT_robustness. Reset status = GL_UNKNOWN_CONTEXT_RESET_KHR [2872:3904:0714/060646:ERROR:gles2_cmd_decoder.cc(5040)] Error: 5 for Command kPostSubBufferCHROMIUM [2872:3904:0714/060646:ERROR:gpu_channel_manager.cc(222)] Exiting GPU process because some drivers cannot recover from problems. Does anyone CC'd have a hypothesis about why this would happen flakily on these tests on this machine?
,
Jul 15 2016
Actually it looks like the problem isn't specific to the video tests. https://build.chromium.org/p/chromium.gpu.fyi/builders/Win7%20Release%20%28New%20Intel%29/builds/1134 is an instance where WebglConformance_deqp_functional_gles3_readpixel failed because the D3D11 device was lost: WebglConformance_deqp_functional_gles3_textureshadow_2d_linear_mipmap_linear_never (gpu_tests.webgl_conformance_integration_test.WebGLConformanceIntegrationTest) ... ok WebglConformance_deqp_functional_gles3_texturefiltering_2d_formats_02 (gpu_tests.webgl_conformance_integration_test.WebGLConformanceIntegrationTest) ... ok WebglConformance_deqp_functional_gles3_readpixel (gpu_tests.webgl_conformance_integration_test.WebGLConformanceIntegrationTest) ... err: rx::Renderer11::testDeviceLost(2616): The D3D11 device was removed: 0x887A0006 [2668:3280:0714/201459:ERROR:gles2_cmd_decoder.cc(4035)] GLES2DecoderImpl: Context lost during MakeCurrent. [2668:3280:0714/201459:ERROR:gpu_command_buffer_stub.cc(387)] Context lost because MakeCurrent failed. [2668:3280:0714/201459:ERROR:gpu_channel_manager.cc(222)] Exiting GPU process because some drivers cannot recover from problems. [2668:3280:0714/201459:ERROR:gpu_channel_manager.cc(222)] Exiting GPU process because some drivers cannot recover from problems. [2668:3280:0714/201459:FATAL:gl_bindings_autogen_gl.cc(12559)] Check failed: false. Trying to call glIsSync() without current GL context Backtrace: base::debug::StackTrace::StackTrace [0x6A2B88B7+23] logging::LogMessage::~LogMessage [0x6A261611+49] gl::NoContextGLApi::glIsSyncFn [0x6A4384B7+82] gl::GLFenceARB::~GLFenceARB [0x6A461548+50] gl::GLFenceARB::`scalar deleting destructor' [0x6A4615C0+11] gpu::gles2::CommandsCompletedQuery::~CommandsCompletedQuery [0x68E3759D+22] scoped_refptr<ppapi::proxy::VarSerializationRules>::Release [0x69025A13+23] std::pair<unsigned int const ,scoped_refptr<gpu::gles2::QueryManager::Query> >::`scalar deleting destructor' [0x68E3771D+20] std::_List_buy<std::pair<unsigned int const ,scoped_refptr<gpu::gles2::QueryManager::Query> >,std::allocator<std::pair<unsigned int const ,scoped_refptr<gpu::gles2::QueryManager::Query> > > >::_Freenode [0x68E39379+17] std::list<std::pair<unsigned int const ,scoped_refptr<gpu::gles2::QueryManager::Query> >,std::allocator<std::pair<unsigned int const ,scoped_refptr<gpu::gles2::QueryManager::Query> > > >::erase [0x68E399D3+41] std::_Hash<std::_Umap_traits<unsigned int,scoped_refptr<gpu::gles2::QueryManager::Query>,std::_Uhash_compare<unsigned int,base_hash::hash<unsigned int>,std::equal_to<unsigned int> >,std::allocator<std::pair<unsigned int const ,scoped_refptr<gpu::gles2::Qu [0x68E39490+49] gpu::gles2::QueryManager::Destroy [0x68E37FDB+75] gpu::gles2::GLES2DecoderImpl::Destroy [0x68DFB202+1257] gpu::GpuCommandBufferStub::Destroy [0x68E59007+308] gpu::GpuCommandBufferStub::~GpuCommandBufferStub [0x68E589A7+22] base::ScopedPtrHashMap<int,std::unique_ptr<media::MediaChannel,std::default_delete<media::MediaChannel> > >::clear [0x68E56F8F+32] base::ScopedPtrHashMap<int,std::unique_ptr<media::MediaChannel,std::default_delete<media::MediaChannel> > >::clear [0x68E56F8F+32] content::GpuChildThread::~GpuChildThread [0x6A0419E2+244] content::ChildProcess::~ChildProcess [0x697BD86A+138] content::GpuMain [0x6A044411+1811] content::RunNamedProcessTypeMain [0x6A24744D+176] content::ContentMainRunnerImpl::Run [0x6A24736C+274] content::ContentMain [0x6A24675B+35] ChromeMain [0x68D0DEB1+97] MainDllLoader::Launch [0x000836EF+488] wWinMain [0x00082DA8+405] __scrt_common_main_seh [0x000F87EF+253] (f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl:255) BaseThreadInitThunk [0x752A338A+18] RtlInitializeExceptionChain [0x77629A02+99] RtlInitializeExceptionChain [0x776299D5+54] ... I think we're going to have to mark all of the WebGL 2.0 tests flaky on Win/Intel. Geoff, Jamie, any comments on this?
,
Jul 15 2016
cwallez mentioned experience resource exhaustion while running WebGL2 conformance test suite. Now we are running even longer, will this be the possible cause of context lost?
,
Jul 15 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/4ba91ad56000b2b4eeb3cfeae0672712e6e77436 commit 4ba91ad56000b2b4eeb3cfeae0672712e6e77436 Author: kbr <kbr@chromium.org> Date: Fri Jul 15 22:03:01 2016 Mark all WebGL 2.0 tests flaky on Win/Intel. BUG= 628395 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel TBR=zmo@chromium.org NOTRY=true Review-Url: https://codereview.chromium.org/2154003002 Cr-Commit-Position: refs/heads/master@{#405872} [modify] https://crrev.com/4ba91ad56000b2b4eeb3cfeae0672712e6e77436/content/test/gpu/gpu_tests/webgl2_conformance_expectations.py
,
Jul 15 2016
It's very possible. The next question would be why we are exhausting resources. When Chrome navigates from page to page, it eagerly shuts down previous pages' WebGL contexts -- or it should be, at least -- and deletes all of their resources. For this reason I don't understand why resource consumption should grow at a large rate. If there's been a regression in this mechanism (which is possible, given refactorings to ActiveDOMObject and WebGLRenderingContext) we should diagnose it ASAP.
,
Aug 18 2016
For some reason, marking the tests as flaky doesn't help. The bot fails with exception from running WebglConformance_conformance2_textures_video_tex* tests: https://build.chromium.org/p/chromium.gpu.fyi/builders/Win7%20Release%20%28New%20Intel%29/builds/1331 - WebglConformance_conformance2_textures_video_tex_3d_rgb565_rgb_unsigned_byte https://build.chromium.org/p/chromium.gpu.fyi/builders/Win7%20Release%20%28New%20Intel%29/builds/1346 - WebglConformance_conformance2_textures_video_tex_2d_rgba16f_rgba_half_float https://build.chromium.org/p/chromium.gpu.fyi/builders/Win7%20Release%20%28New%20Intel%29/builds/1347 - WebglConformance_conformance2_textures_video_tex_2d_rgba16f_rgba_half_float
,
Aug 18 2016
,
Aug 18 2016
I don't know why the log ends when the harness attempts to relaunch the browser, nor why the recipe aborts at that point. You could try logging on to the bot via the Raritan (see the GPU internal pixel wrangling instructions) and try a run with one of the same isolates and use the --test-filter= flag to run just the video tests.
,
Aug 18 2016
Media folks: these tests were previously running reliably; did something change in the media stack to make it less resistant to failures?
,
Aug 18 2016
Yuly, can you please try logging on to the bot via the Raritan (see the GPU Internal Pixel Wrangling Instructions) and see if you can reproduce the failure manually?
,
Aug 18 2016
OK, I'll try.
,
Aug 19 2016
Don't see any fatal media errors in that log. There are some errors listed, but they all should recover normally (And appear to do so per the log).
,
Oct 4 2016
,
Oct 4 2016
,
Oct 27 2016
I think I may have a possible hint for the reason of this failure (can also be an unrelated failure), and it's coming from Mac AMD. https://build.chromium.org/p/chromium.gpu.fyi/builders/Mac%2010.10%20Retina%20Debug%20%28AMD%29/builds/12296 WebglConformance_conformance_textures_video_tex_2d_rgb_rgb_unsigned_short_5_6_5 (gpu_tests.webgl_conformance_integration_test.WebGLConformanceIntegrationTest) ... [1529:18947:1026/035952:FATAL:video_renderer_algorithm.cc(308)] Check failed: frame_queue_.front().drop_count <= frame_queue_.front().render_count (2 vs. 1) 0 libbase.dylib 0x0000000122630e0e _ZN4base5debug10StackTraceC2Ev + 30 1 libbase.dylib 0x0000000122630e75 _ZN4base5debug10StackTraceC1Ev + 21 2 libbase.dylib 0x00000001226c9e30 _ZN7logging10LogMessageD2Ev + 80 3 libbase.dylib 0x00000001226c79e5 _ZN7logging10LogMessageD1Ev + 21 4 libmedia.dylib 0x00000001338baa8e _ZN5media22VideoRendererAlgorithm18OnLastFrameDroppedEv + 734 5 libmedia.dylib 0x0000000133959bf7 _ZN5media17VideoRendererImpl14OnFrameDroppedEv + 103 6 libmedia_blink.dylib 0x000000013de24049 _ZN5media20VideoFrameCompositor10CallRenderEN4base9TimeTicksES2_b + 713 7 libmedia_blink.dylib 0x000000013de23d41 _ZN5media20VideoFrameCompositor18UpdateCurrentFrameEN4base9TimeTicksES2_ + 321 8 libcc.dylib 0x00000001348ffcc4 _ZN2cc28VideoFrameProviderClientImpl12OnBeginFrameERKNS_14BeginFrameArgsE + 1140 9 libcc.dylib 0x0000000134c086b4 _ZN2cc17LayerTreeHostImpl18WillBeginImplFrameERKNS_14BeginFrameArgsE + 804 10 libcc.dylib 0x0000000134cecad3 _ZN2cc9ProxyImpl18WillBeginImplFrameERKNS_14BeginFrameArgsE + 323 11 libcc.dylib 0x0000000134afb7fa _ZN2cc9Scheduler14BeginImplFrameERKNS_14BeginFrameArgsE + 890 12 libcc.dylib 0x0000000134afa52a _ZN2cc9Scheduler26BeginImplFrameWithDeadlineERKNS_14BeginFrameArgsE + 3130 13 libcc.dylib 0x0000000134af9493 _ZN2cc9Scheduler23OnBeginFrameDerivedImplERKNS_14BeginFrameArgsE + 1923 14 libcc.dylib 0x0000000134ad6b8b _ZN2cc22BeginFrameObserverBase12OnBeginFrameERKNS_14BeginFrameArgsE + 491 15 libcc.dylib 0x0000000134ae1487 _ZN2cc24ExternalBeginFrameSource12OnBeginFrameERKNS_14BeginFrameArgsE + 695 16 libcontent.dylib 0x000000012ac5c4fc _ZN7content34CompositorExternalBeginFrameSource12OnBeginFrameERKN2cc14BeginFrameArgsE + 44 17 libcontent.dylib 0x000000012ac5d6cd _ZN4base20DispatchToMethodImplIPN7content34CompositorExternalBeginFrameSourceEMS2_FvRKN2cc14BeginFrameArgsEERKNSt3__15tupleIJS5_EEEJLm0EEEEvRKT_T0_OT1_NS_13IndexSequenceIJXspT2_EEEE + 157 18 libcontent.dylib 0x000000012ac5d620 _ZN4base16DispatchToMethodIPN7content34CompositorExternalBeginFrameSourceEMS2_FvRKN2cc14BeginFrameArgsEERKNSt3__15tupleIJS5_EEEEEvRKT_T0_OT1_ + 96 19 libcontent.dylib 0x000000012ac5d59d _ZN3IPC16DispatchToMethodIN7content34CompositorExternalBeginFrameSourceEMS2_FvRKN2cc14BeginFrameArgsEEvNSt3__15tupleIJS4_EEEEEvPT_T0_PT1_RKT2_ + 109 20 libcontent.dylib 0x000000012ac5c456 _ZN3IPC8MessageTI23ViewMsg_BeginFrame_MetaNSt3__15tupleIJN2cc14BeginFrameArgsEEEEvE8DispatchIN7content34CompositorExternalBeginFrameSourceESA_vMSA_FvRKS5_EEEbPKNS_7MessageEPT_PT0_PT1_T2_ + 518 21 libcontent.dylib 0x000000012ac5bf87 _ZN7content34CompositorExternalBeginFrameSource17OnMessageReceivedERKN3IPC7MessageE + 903 22 libcontent.dylib 0x000000012ac5b9c4 _ZN7content34CompositorExternalBeginFrameSource39CompositorExternalBeginFrameSourceProxy17OnMessageReceivedERKN3IPC7MessageE + 52 23 libcontent.dylib 0x000000012ac5cbe7 _ZN4base8internal13FunctorTraitsIMN7content34CompositorExternalBeginFrameSource39CompositorExternalBeginFrameSourceProxyEFvRKN3IPC7MessageEEvE6InvokeIRK13scoped_refptrIS4_EJS8_EEEvSA_OT_DpOT0_ + 151 24 libcontent.dylib 0x000000012ac5caef _ZN4base8internal12InvokeHelperILb0EvE8MakeItSoIRKMN7content34CompositorExternalBeginFrameSource39CompositorExternalBeginFrameSourceProxyEFvRKN3IPC7MessageEEJRK13scoped_refptrIS6_ESA_EEEvOT_DpOT0_ + 95 25 libcontent.dylib 0x000000012ac5ca88 _ZN4base8internal7InvokerINS0_9BindStateIMN7content34CompositorExternalBeginFrameSource39CompositorExternalBeginFrameSourceProxyEFvRKN3IPC7MessageEEJ13scoped_refptrIS5_EEEEFvS9_EE7RunImplIRKSB_RKNSt3__15tupleIJSD_EEEJLm0EEEEvOT_OT0_NS_13IndexSequenceIJXspT1_EEEES9_ + 88 26 libcontent.dylib 0x000000012ac5c9a4 _ZN4base8internal7InvokerINS0_9BindStateIMN7content34CompositorExternalBeginFrameSource39CompositorExternalBeginFrameSourceProxyEFvRKN3IPC7MessageEEJ13scoped_refptrIS5_EEEEFvS9_EE3RunEPNS0_13BindStateBaseES9_ + 68 27 libcontent.dylib 0x000000012ac5eb81 _ZNK4base8internal8RunMixinINS_8CallbackIFvRKN3IPC7MessageEELNS0_8CopyModeE1ELNS0_10RepeatModeE1EEEE3RunES6_ + 81 28 libcontent.dylib 0x000000012ac5e9ea _ZN7content33CompositorForwardingMessageFilter32ProcessMessageOnCompositorThreadERKN3IPC7MessageE + 1018 29 libcontent.dylib 0x000000012ac60b57 _ZN4base8internal13FunctorTraitsIMN7content33CompositorForwardingMessageFilterEFvRKN3IPC7MessageEEvE6InvokeIRK13scoped_refptrIS3_EJS7_EEEvS9_OT_DpOT0_ + 151 30 libcontent.dylib 0x000000012ac60a2f _ZN4base8internal12InvokeHelperILb0EvE8MakeItSoIRKMN7content33CompositorForwardingMessageFilterEFvRKN3IPC7MessageEEJRK13scoped_refptrIS5_ES9_EEEvOT_DpOT0_ + 95 31 libcontent.dylib 0x000000012ac609c9 _ZN4base8internal7InvokerINS0_9BindStateIMN7content33CompositorForwardingMessageFilterEFvRKN3IPC7MessageEEJ13scoped_refptrIS4_ES6_EEEFvvEE7RunImplIRKSA_RKNSt3__15tupleIJSC_S6_EEEJLm0ELm1EEEEvOT_OT0_NS_13IndexSequenceIJXspT1_EEEE + 105 32 libcontent.dylib 0x000000012ac608ec _ZN4base8internal7InvokerINS0_9BindStateIMN7content33CompositorForwardingMessageFilterEFvRKN3IPC7MessageEEJ13scoped_refptrIS4_ES6_EEEFvvEE3RunEPNS0_13BindStateBaseE + 44 33 libbase.dylib 0x0000000122632c0a _ZNO4base8internal8RunMixinINS_8CallbackIFvvELNS0_8CopyModeE0ELNS0_10RepeatModeE0EEEE3RunEv + 90 34 libbase.dylib 0x000000012263298f _ZN4base5debug13TaskAnnotator7RunTaskEPKcPNS_11PendingTaskE + 687 35 libbase.dylib 0x000000012271d1cb _ZN4base11MessageLoop7RunTaskEPNS_11PendingTaskE + 923 36 libbase.dylib 0x000000012271d744 _ZN4base11MessageLoop21DeferOrRunPendingTaskENS_11PendingTaskE + 68 37 libbase.dylib 0x000000012271e17d _ZN4base11MessageLoop6DoWorkEv + 669 38 libbase.dylib 0x00000001227300d8 _ZN4base24MessagePumpCFRunLoopBase7RunWorkEv + 104 39 libbase.dylib 0x000000012273005c ___ZN4base24MessagePumpCFRunLoopBase13RunWorkSourceEPv_block_invoke + 28 40 libbase.dylib 0x00000001226cddda _ZN4base3mac15CallWithEHFrameEU13block_pointerFvvE + 10 41 libbase.dylib 0x000000012272f5d5 _ZN4base24MessagePumpCFRunLoopBase13RunWorkSourceEPv + 101 42 CoreFoundation 0x00007fff937f8881 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17 43 CoreFoundation 0x00007fff937d7fbc __CFRunLoopDoSources0 + 556 44 CoreFoundation 0x00007fff937d74df __CFRunLoopRun + 927 45 CoreFoundation 0x00007fff937d6ed8 CFRunLoopRunSpecific + 296 46 libbase.dylib 0x000000012273073c _ZN4base20MessagePumpCFRunLoop5DoRunEPNS_11MessagePump8DelegateE + 76 47 libbase.dylib 0x000000012272fdba _ZN4base24MessagePumpCFRunLoopBase3RunEPNS_11MessagePump8DelegateE + 122 48 libbase.dylib 0x000000012271cc55 _ZN4base11MessageLoop10RunHandlerEv + 645 49 libbase.dylib 0x00000001227ec285 _ZN4base7RunLoop3RunEv + 85 50 libbase.dylib 0x00000001228e83cc _ZN4base6Thread3RunEPNS_7RunLoopE + 428 51 libbase.dylib 0x00000001228e95f8 _ZN4base6Thread10ThreadMainEv + 3512 52 libbase.dylib 0x00000001228c2101 _ZN4base12_GLOBAL__N_110ThreadFuncEPv + 705 53 libsystem_pthread.dylib 0x00007fff8f0fe99d _pthread_body + 131 54 libsystem_pthread.dylib 0x00007fff8f0fe91a _pthread_body + 0 55 libsystem_pthread.dylib 0x00007fff8f0fc351 thread_start + 13
,
Oct 27 2016
That's a new flake, fix is in flight, issue 656231
,
Nov 2 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/47c697f769a1491c1d14581a0daffacdbccef472 commit 47c697f769a1491c1d14581a0daffacdbccef472 Author: cwallez <cwallez@chromium.org> Date: Wed Nov 02 20:07:03 2016 WebGL CTS: remove suppressions for passing tests TBR=zmo@chromium.org BUG= angleproject:1007 BUG= angleproject:1277 BUG= angleproject:1246 BUG=angleproject:1312 BUG= chromium:483282 BUG= chromium:540543 BUG= chromium:544989 BUG= chromium:598924 BUG= chromium:610800 BUG= chromium:614418 BUG= chromium:628395 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel Review-Url: https://codereview.chromium.org/2468293002 Cr-Commit-Position: refs/heads/master@{#429381} [modify] https://crrev.com/47c697f769a1491c1d14581a0daffacdbccef472/content/test/gpu/gpu_tests/webgl2_conformance_expectations.py [modify] https://crrev.com/47c697f769a1491c1d14581a0daffacdbccef472/content/test/gpu/gpu_tests/webgl_conformance_expectations.py
,
Nov 3 2017
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. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 3 2017
These machines have since been replaced. No longer reproducible.
,
Jan 15
|
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by kbr@chromium.org
, Jul 14 2016