angle_end2end_tests flaky on Win7 Release (AMD R5 230) |
||
Issue descriptionExample failing build: https://build.chromium.org/p/chromium.gpu.fyi/builders/Win7%20Release%20%28AMD%20R5%20230%29/builds/338 [ RUN ] Texture2DNorm16TestES3.TextureNorm16Test/ES3_D3D11 e:\b\c\b\win\src\third_party\angle\src\tests\gl_tests\texturetest.cpp(3353): error: Value of: angle::ReadColor(0, 0) Actual: (255, 255, 0, 255) Expected: SliceFormatColor(format, GLColor::white) Which is: (255, 255, 255, 255) [ FAILED ] Texture2DNorm16TestES3.TextureNorm16Test/ES3_D3D11, where GetParam() = ES3_D3D11 (79 ms)
,
Dec 20 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/7e2473b005699b9adac0246c3f3aba6f31471c4f commit 7e2473b005699b9adac0246c3f3aba6f31471c4f Author: jmadill <jmadill@chromium.org> Date: Tue Dec 20 16:30:04 2016 Disable angle_end2end_tests on Win/old AMD. These tests are flaky, and until we can figure out how to enable retries only on this config, we should disable them. BUG= 674932 TBR=kbr@chromium.org,ynovikov@chromium.org NOTRY=true 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/2594713002 Cr-Commit-Position: refs/heads/master@{#439819} [modify] https://crrev.com/7e2473b005699b9adac0246c3f3aba6f31471c4f/content/test/gpu/generate_buildbot_json.py [modify] https://crrev.com/7e2473b005699b9adac0246c3f3aba6f31471c4f/testing/buildbot/chromium.gpu.fyi.json
,
Nov 13 2017
We removed the R5 230 config. |
||
►
Sign in to add a comment |
||
Comment 1 by jmad...@chromium.org
, Dec 16 2016