GLClearFramebufferTest.ClearDepthStencil has a D3D11 device loss on Intel |
|||||||||||
Issue descriptionThe GLClearFramebufferTestWithParam/GLClearFramebufferTest.ClearDepthStencil/0 test from Chrome's gl_tests suite results in a device loss on top of ANGLE D3D11. Failure: https://build.chromium.org/p/chromium.gpu.fyi/builders/Win10%20Release%20%28Intel%20HD%20630%29/builds/980 Log: ../../gpu/command_buffer/tests/gl_test_utils.cc(183): error: Expected: expected Which is: '\xFF' (255) To be equal to: actual Which is: '\x4' (4) at 0, 0 channel 0 ../../gpu/command_buffer/tests/gl_test_utils.cc(183): error: Expected: expected Which is: '\0' To be equal to: actual Which is: '\x4' (4) at 0, 0 channel 1 ../../gpu/command_buffer/tests/gl_test_utils.cc(183): error: Expected: expected Which is: '\0' To be equal to: actual Which is: '\x4' (4) at 0, 0 channel 2 ../../gpu/command_buffer/tests/gl_test_utils.cc(183): error: Expected: expected Which is: '\xFF' (255) To be equal to: actual Which is: '\x4' (4) at 0, 0 channel 3 ../../gpu/command_buffer/tests/gl_clear_framebuffer_unittest.cc(197): error: Value of: GLTestHelper::CheckPixels(0, 0, 1, 1, 0 , kRed, nullptr) Actual: false Expected: true D3D11: Removing Device. D3D11 ERROR: ID3D11Device::RemoveDevice: Device removal has been triggered for the following reason (DXGI_ERROR_DEVICE_HUNG: The Device took an unreasonable amount of time to execute its commands, or the hardware crashed/hung. As a result, the TDR (Timeout Detection and Recovery) mechanism has been triggered. The current Device Context was executing commands when the hang occurred. The application may want to respawn and fallback to less aggressive use of the display hardware). [ EXECUTION ERROR #378: DEVICE_REMOVAL_PROCESS_AT_FAULT] The issue reproduces for me on a Intel 630 GPU (Dell OptiPlex 7050), I have not tried it on other Intel systems. The issue does not reproduce on a WARP device. Yang, care to assign this? I can look into it more if needed.
,
Nov 10 2017
The test case can pass on Intel if turn off workaround gl_clear_broken (https://codereview.chromium.org/719503003).I will remove this limitation on Intel platforms.
,
Nov 14 2017
cc'ing piman because the first failing build had clear changes in the regression range: https://chromium-review.googlesource.com/753823 https://chromium-review.googlesource.com/754361 First failing: https://ci.chromium.org/buildbot/chromium.gpu.fyi/Win10%20Release%20%28Intel%20HD%20630%29/976
,
Nov 14 2017
This was likely introduced by https://chromium-review.googlesource.com/c/chromium/src/+/753823, but that means drawing an arbitrarily large quad triggers a lost device.
,
Nov 15 2017
yizhou.jiang: I'm suppressing the failing test on our test bots. Will you be adding a workaround? If you do, please remove this suppression at the same time. https://crrev.com/c/772799
,
Nov 15 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/35215c489a5952f84446b5bf132d06867759b480 commit 35215c489a5952f84446b5bf132d06867759b480 Author: Kai Ninomiya <kainino@chromium.org> Date: Wed Nov 15 20:21:36 2017 Suppress GLClearFramebufferTest.ClearDepthStencil on Intel TBR=kbr@chromium.org Bug: 782317 Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;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 Change-Id: I7e47214c01fdc22e8815e4ce8e969f54c1365785 Reviewed-on: https://chromium-review.googlesource.com/772799 Commit-Queue: Kai Ninomiya <kainino@chromium.org> Reviewed-by: Kenneth Russell <kbr@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org> Cr-Commit-Position: refs/heads/master@{#516803} [modify] https://crrev.com/35215c489a5952f84446b5bf132d06867759b480/gpu/command_buffer/tests/gl_clear_framebuffer_unittest.cc
,
Nov 16 2017
@kainino, ok, I will try to write an webgl cts test to catch the bug first.
,
Dec 1 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/92329226aa13dbee68b0898ca1fd21c17fd61652 commit 92329226aa13dbee68b0898ca1fd21c17fd61652 Author: JiangYizhou <yizhou.jiang@intel.com> Date: Fri Dec 01 17:42:23 2017 Roll WebGL e4919fa..05591bb https://chromium.googlesource.com/external/khronosgroup/webgl.git/+log/e4919fa..05591bb BUG=782317 TEST=bots CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;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 Change-Id: Ib9d1d373b8942214cf655d6aa132dddd233229a0 Reviewed-on: https://chromium-review.googlesource.com/802696 Reviewed-by: Yunchao He <yunchao.he@intel.com> Reviewed-by: Zhenyao Mo <zmo@chromium.org> Commit-Queue: Zhenyao Mo <zmo@chromium.org> Cr-Commit-Position: refs/heads/master@{#520976} [modify] https://crrev.com/92329226aa13dbee68b0898ca1fd21c17fd61652/DEPS [modify] https://crrev.com/92329226aa13dbee68b0898ca1fd21c17fd61652/content/test/gpu/gpu_tests/webgl2_conformance_expectations.py [modify] https://crrev.com/92329226aa13dbee68b0898ca1fd21c17fd61652/content/test/gpu/gpu_tests/webgl_conformance_revision.txt
,
Dec 2 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/5c99cf327e783e360d49ce86df110c628d1b8336 commit 5c99cf327e783e360d49ce86df110c628d1b8336 Author: Yunchao He <yunchao.he@intel.com> Date: Sat Dec 02 05:29:31 2017 Update webgl expectations BUG=782317 TEST=bots Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;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 Change-Id: I96ae1e737dc2ce91a08c930110bc7bf16ce97bbf Reviewed-on: https://chromium-review.googlesource.com/804684 Commit-Queue: Yunchao He <yunchao.he@intel.com> Commit-Queue: Kenneth Russell <kbr@chromium.org> Reviewed-by: Kenneth Russell <kbr@chromium.org> Cr-Commit-Position: refs/heads/master@{#521200} [modify] https://crrev.com/5c99cf327e783e360d49ce86df110c628d1b8336/content/test/gpu/gpu_tests/webgl2_conformance_expectations.py [modify] https://crrev.com/5c99cf327e783e360d49ce86df110c628d1b8336/content/test/gpu/gpu_tests/webgl_conformance_expectations.py
,
Jan 2 2018
The following revision refers to this bug: https://chromium.googlesource.com/angle/angle/+/63ba357c093954d2bc475867e1296fbf5afc1d37 commit 63ba357c093954d2bc475867e1296fbf5afc1d37 Author: JiangYizhou <yizhou.jiang@intel.com> Date: Tue Jan 02 16:23:40 2018 Enable depth buffer to workaround driver bug on Intel windows Rendering with depth buffer disabled and stencil buffer enabled leads to memory leak if we set viewport a large size on Intel windows platforms. So we enable depth buffer if stencil buffer is enabled to workaround this issue. TEST=gl_test.exe --gtest_filter=GLClearFramebufferTestWithParam/GLClearFramebufferTest.ClearDepthStencil/0 TEST=conformance/rendering/rendering-stencil-large-viewport.html TEST=RenderStencilBufferTest.DrawWithLargeViewport/ES3_D3D11 BUG=782317 Change-Id: Idb185db296f13e3fa897534514e198651a56439f Reviewed-on: https://chromium-review.googlesource.com/809574 Commit-Queue: Jamie Madill <jmadill@chromium.org> Reviewed-by: Jamie Madill <jmadill@chromium.org> [modify] https://crrev.com/63ba357c093954d2bc475867e1296fbf5afc1d37/src/libANGLE/renderer/d3d/d3d11/renderer11_utils.cpp [add] https://crrev.com/63ba357c093954d2bc475867e1296fbf5afc1d37/src/tests/gl_tests/RenderStencilBufferTest.cpp [modify] https://crrev.com/63ba357c093954d2bc475867e1296fbf5afc1d37/src/libANGLE/renderer/d3d/d3d11/RenderStateCache.cpp [modify] https://crrev.com/63ba357c093954d2bc475867e1296fbf5afc1d37/src/tests/angle_end2end_tests.gypi [modify] https://crrev.com/63ba357c093954d2bc475867e1296fbf5afc1d37/include/platform/WorkaroundsD3D.h
,
Jan 3 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/0edc6b5a6ab9575db5f69cd104e9bc34c064854c commit 0edc6b5a6ab9575db5f69cd104e9bc34c064854c Author: angle-deps-roller@chromium.org <angle-deps-roller@chromium.org> Date: Wed Jan 03 05:27:35 2018 Roll src/third_party/angle/ 8c3988c59..c8c9a24a1 (9 commits) https://chromium.googlesource.com/angle/angle.git/+log/8c3988c59ebe..c8c9a24a117a $ git log 8c3988c59..c8c9a24a1 --date=short --no-merges --format='%ad %ae %s' 2018-01-02 jmadill Entry Points: Refactor generator script. 2017-12-29 oetuaho Simplify creating the call DAG 2018-01-02 jmadill VertexArray: Add enabled attribs bitmask. 2017-12-28 jmadill Entry Points: Speed up auto-gen. 2017-12-20 jiawei.shao ES31: Clean up Program::link 2017-12-06 yizhou.jiang Enable depth buffer to workaround driver bug on Intel windows 2017-12-12 oetuaho Clean up creating constant folded nodes 2017-12-20 oetuaho Unify looking for symbols with a specific name in the AST 2017-12-13 jiawei.shao ES31: Support struct arrays as Geometry Shader inputs Created with: roll-dep src/third_party/angle BUG=782317 The AutoRoll server is located here: https://angle-chromium-roll.skia.org Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;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=jmadill@chromium.org Change-Id: I928d4f21878a87834bff362e3a405c40b8fdadb1 Reviewed-on: https://chromium-review.googlesource.com/848375 Commit-Queue: angle-deps-roller . <angle-deps-roller@chromium.org> Reviewed-by: angle-deps-roller . <angle-deps-roller@chromium.org> Cr-Commit-Position: refs/heads/master@{#526626} [modify] https://crrev.com/0edc6b5a6ab9575db5f69cd104e9bc34c064854c/DEPS
,
Jan 3 2018
The following revision refers to this bug: https://chromium.googlesource.com/angle/angle/+/36937a64f438a2e0c166f99d90ced59c5dbbb1be commit 36937a64f438a2e0c166f99d90ced59c5dbbb1be Author: Jamie Madill <jmadill@chromium.org> Date: Wed Jan 03 20:15:05 2018 Revert "Enable depth buffer to workaround driver bug on Intel windows" This reverts commit 63ba357c093954d2bc475867e1296fbf5afc1d37. Reason for revert: May be causing Windows GPU.FYI bot failures. https://ci.chromium.org/buildbot/chromium.gpu.fyi/Win10%20Release%20%28Intel%20HD%20630%29/1443 maps_pixel_test on Intel GPU: Unexpected Failures: * gpu_tests.maps_integration_test.MapsIntegrationTest.Maps_maps webgl2_conformance_tests on Intel GPU: Unexpected Failures: * gpu_tests.webgl_conformance_integration_test.WebGLConformanceIntegrationTest.WebglConformance_deqp_functional_gles3_fboinvalidate_default * gpu_tests.webgl_conformance_integration_test.WebGLConformanceIntegrationTest.WebglConformance_deqp_functional_gles3_fboinvalidate_sub Bug: chromium:798757 Original change's description: > Enable depth buffer to workaround driver bug on Intel windows > > Rendering with depth buffer disabled and stencil buffer enabled > leads to memory leak if we set viewport a large size on Intel > windows platforms. So we enable depth buffer if stencil buffer > is enabled to workaround this issue. > > TEST=gl_test.exe --gtest_filter=GLClearFramebufferTestWithParam/GLClearFramebufferTest.ClearDepthStencil/0 > TEST=conformance/rendering/rendering-stencil-large-viewport.html > TEST=RenderStencilBufferTest.DrawWithLargeViewport/ES3_D3D11 > > BUG=782317 > > Change-Id: Idb185db296f13e3fa897534514e198651a56439f > Reviewed-on: https://chromium-review.googlesource.com/809574 > Commit-Queue: Jamie Madill <jmadill@chromium.org> > Reviewed-by: Jamie Madill <jmadill@chromium.org> TBR=zmo@chromium.org,geofflang@chromium.org,jmadill@chromium.org,kbr@chromium.org,cwallez@chromium.org,yunchao.he@intel.com,jiajia.qin@intel.com,xinghua.cao@intel.com,bryan.bernhart@intel.com,yizhou.jiang@intel.com,yang.gu@intel.com # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 782317 Change-Id: I7e29da683b22fd4640c230598c7b220cfae6a177 Reviewed-on: https://chromium-review.googlesource.com/848133 Commit-Queue: Jamie Madill <jmadill@chromium.org> Reviewed-by: Jamie Madill <jmadill@chromium.org> [modify] https://crrev.com/36937a64f438a2e0c166f99d90ced59c5dbbb1be/src/libANGLE/renderer/d3d/d3d11/renderer11_utils.cpp [delete] https://crrev.com/8b5e8fdb3c353d46c81243b31889856181ff66ae/src/tests/gl_tests/RenderStencilBufferTest.cpp [modify] https://crrev.com/36937a64f438a2e0c166f99d90ced59c5dbbb1be/src/libANGLE/renderer/d3d/d3d11/RenderStateCache.cpp [modify] https://crrev.com/36937a64f438a2e0c166f99d90ced59c5dbbb1be/src/tests/angle_end2end_tests.gypi [modify] https://crrev.com/36937a64f438a2e0c166f99d90ced59c5dbbb1be/include/platform/WorkaroundsD3D.h
,
Jan 3 2018
,
Feb 22 2018
The following revision refers to this bug: https://chromium.googlesource.com/angle/angle/+/1dce1bd38e1b89c41b28e7e980643651670b595a commit 1dce1bd38e1b89c41b28e7e980643651670b595a Author: JiangYizhou <yizhou.jiang@intel.com> Date: Thu Feb 22 17:12:38 2018 Add test case to catch depth stencil buffer bug on Intel windows Rendering with depth buffer disabled and stencil buffer enabled leads to memory leak if we set viewport a large size on Intel windows platforms. Add an end2end test case to catch this driver bug. TEST=DepthStencilFormatsTestES3.DrawWithLargeViewport/ES3_D3D11 BUG=782317 Change-Id: I16efb9459717e94e2edb5d5eb5dc24f47d746ea3 Reviewed-on: https://chromium-review.googlesource.com/858430 Commit-Queue: Geoff Lang <geofflang@chromium.org> Reviewed-by: Jamie Madill <jmadill@chromium.org> [modify] https://crrev.com/1dce1bd38e1b89c41b28e7e980643651670b595a/src/tests/gl_tests/DepthStencilFormatsTest.cpp
,
Feb 22 2018
The following revision refers to this bug: https://skia.googlesource.com/skia/+/2c0349262132d6aa54ac6e8a4295f17c67e25907 commit 2c0349262132d6aa54ac6e8a4295f17c67e25907 Author: angle-skia-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com <angle-skia-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Thu Feb 22 18:00:39 2018 Roll skia/third_party/externals/angle2/ 24842908c..1dce1bd38 (1 commit) https://chromium.googlesource.com/angle/angle.git/+log/24842908c4bd..1dce1bd38e1b $ git log 24842908c..1dce1bd38 --date=short --no-merges --format='%ad %ae %s' 2017-12-06 yizhou.jiang Add test case to catch depth stencil buffer bug on Intel windows Created with: roll-dep skia/third_party/externals/angle2 BUG=782317 The AutoRoll server is located here: https://angle-skia-roll.skia.org Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=skia.primary:Perf-Win10-Clang-AlphaR2-GPU-RadeonR9M470X-x86_64-Debug-All-ANGLE,Perf-Win10-Clang-NUC5i7RYH-GPU-IntelIris6100-x86_64-Debug-All-ANGLE,Perf-Win10-Clang-NUC6i5SYK-GPU-IntelIris540-x86_64-Debug-All-ANGLE,Perf-Win10-Clang-NUCD34010WYKH-GPU-IntelHD4400-x86_64-Debug-All-ANGLE,Perf-Win10-Clang-ShuttleC-GPU-GTX960-x86_64-Debug-All-ANGLE,Test-Win10-Clang-AlphaR2-GPU-RadeonR9M470X-x86_64-Debug-All-ANGLE,Test-Win10-Clang-NUC6i5SYK-GPU-IntelIris540-x86_64-Debug-All-ANGLE,Test-Win10-Clang-NUCD34010WYKH-GPU-IntelHD4400-x86_64-Debug-All-ANGLE,Test-Win10-Clang-ShuttleC-GPU-GTX960-x86_64-Debug-All-ANGLE,Build-Debian9-Clang-x86_64-Release-ANGLE TBR=djsollen@google.com Change-Id: I0c9a3ed235de7956a76cb4aaaa0e25a696283426 Reviewed-on: https://skia-review.googlesource.com/109344 Reviewed-by: <angle-skia-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: <angle-skia-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> [modify] https://crrev.com/2c0349262132d6aa54ac6e8a4295f17c67e25907/DEPS
,
Feb 22 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fdc4169babba9e41dea5f07fa851ee6d3624762a commit fdc4169babba9e41dea5f07fa851ee6d3624762a Author: angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Thu Feb 22 19:16:37 2018 Roll src/third_party/angle/ 24842908c..1dce1bd38 (1 commit) https://chromium.googlesource.com/angle/angle.git/+log/24842908c4bd..1dce1bd38e1b $ git log 24842908c..1dce1bd38 --date=short --no-merges --format='%ad %ae %s' 2017-12-06 yizhou.jiang Add test case to catch depth stencil buffer bug on Intel windows Created with: roll-dep src/third_party/angle BUG=782317 The AutoRoll server is located here: https://angle-chromium-roll.skia.org Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;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=fjhenigman@chromium.org Change-Id: I00583b463edc069303a78cf9564c83903a86e675 Reviewed-on: https://chromium-review.googlesource.com/931753 Reviewed-by: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#538516} [modify] https://crrev.com/fdc4169babba9e41dea5f07fa851ee6d3624762a/DEPS
,
Feb 22 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/f3c15f188cdd4b532f4f283283dc125c9bcb5746 commit f3c15f188cdd4b532f4f283283dc125c9bcb5746 Author: skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Thu Feb 22 20:22:07 2018 Roll src/third_party/skia/ 085bc5236..2c0349262 (5 commits) https://skia.googlesource.com/skia.git/+log/085bc523634e..2c0349262132 $ git log 085bc5236..2c0349262 --date=short --no-merges --format='%ad %ae %s' 2018-02-22 angle-skia-autoroll Roll skia/third_party/externals/angle2/ 24842908c..1dce1bd38 (1 commit) 2018-02-22 borenet Add bot which builds without DEPS 2018-02-22 reed detect bad radius in cornerpatheffect 2018-02-22 skcms-skia-autoroll Roll skia/third_party/externals/skcms/ 422746635..2f0bbab5e (1 commit) 2018-02-22 herb Small cleanup of SkPaint Created with: roll-dep src/third_party/skia BUG=782317 The AutoRoll server is located here: https://autoroll.skia.org Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;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=djsollen@chromium.org Change-Id: Ibf0bcb29516173ee7f3ed6f41d9c2f9185fcc1e2 Reviewed-on: https://chromium-review.googlesource.com/932006 Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Reviewed-by: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#538544} [modify] https://crrev.com/f3c15f188cdd4b532f4f283283dc125c9bcb5746/DEPS
,
Mar 27 2018
Hi Ken, this bug is also detected on mac on Intel. I've wrote a radar, could you help to review the document and report to Apple? Thanks. https://docs.google.com/document/d/1xetVKXju7p4viXD0L2uXtaeKx8rsYX5wlVv5MKRlx1I/edit Btw, the bug has been fixed on Windows by Intel driver team.
,
Mar 27 2018
,
Mar 28 2018
I'll take care of relaying this.
,
Mar 28 2018
I ran this test a few times on my laptop (MacBook Air Early 2015, Intel HD 6000) and it appeared flaky (it seems to alternate fail, pass, fail, pass). After about 6 runs, it actually hung and crashed the entire system. I've reproduced this 3 times. So I'm editing the report, capturing appropriate diagnostic information, and submitted it as Crash/Hang/Data Loss.
,
Mar 28 2018
,
Mar 29 2018
Filed Radar 38979529
,
Mar 29 2018
,
Jul 17
Verified that the test flakiness and system hang reported in Radar 38979529 is fixed in macOS 10.14 beta (18A336e). Tested on a MacBook Air (13-inch, Early 2015) with Intel HD Graphics 6000 1536 MB.
,
Nov 27
,
Nov 27
|
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by yang...@intel.com
, Nov 8 2017Owner: yizhou.j...@intel.com