"gpu_rasterization_tests (with patch)" is flaky |
||||
Issue description"gpu_rasterization_tests (with patch)" 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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyLwsSBUZsYWtlIiRncHVfcmFzdGVyaXphdGlvbl90ZXN0cyAod2l0aCBwYXRjaCkM. This flaky test/step was previously tracked in issue 675303 .
,
Dec 29 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/abf38db92dc4cfecaa8e58cb4f8925414b8607d5 commit abf38db92dc4cfecaa8e58cb4f8925414b8607d5 Author: kbr <kbr@chromium.org> Date: Thu Dec 29 08:57:02 2016 Fold the GPU rasterization tests into the pixel tests step. This has the side-effect of using the new GPU integration test harness for these tests. BUG= 352807 , 676701 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 TBR=zmo@chromium.org Review-Url: https://codereview.chromium.org/2607073002 Cr-Commit-Position: refs/heads/master@{#440947} [modify] https://crrev.com/abf38db92dc4cfecaa8e58cb4f8925414b8607d5/content/test/gpu/generate_buildbot_json.py [delete] https://crrev.com/6f744e69aed7cb03be7bc578aa4859a43d2ef269/content/test/gpu/gpu_tests/gpu_rasterization.py [delete] https://crrev.com/6f744e69aed7cb03be7bc578aa4859a43d2ef269/content/test/gpu/gpu_tests/gpu_rasterization_expectations.py [delete] https://crrev.com/6f744e69aed7cb03be7bc578aa4859a43d2ef269/content/test/gpu/gpu_tests/memory_test_expectations.py [modify] https://crrev.com/abf38db92dc4cfecaa8e58cb4f8925414b8607d5/content/test/gpu/gpu_tests/pixel_expectations.py [modify] https://crrev.com/abf38db92dc4cfecaa8e58cb4f8925414b8607d5/content/test/gpu/gpu_tests/pixel_integration_test.py [modify] https://crrev.com/abf38db92dc4cfecaa8e58cb4f8925414b8607d5/content/test/gpu/gpu_tests/pixel_test_pages.py [modify] https://crrev.com/abf38db92dc4cfecaa8e58cb4f8925414b8607d5/content/test/gpu/page_sets/__init__.py [delete] https://crrev.com/6f744e69aed7cb03be7bc578aa4859a43d2ef269/content/test/gpu/page_sets/gpu_rasterization_tests.py [modify] https://crrev.com/abf38db92dc4cfecaa8e58cb4f8925414b8607d5/testing/buildbot/chromium.gpu.fyi.json [modify] https://crrev.com/abf38db92dc4cfecaa8e58cb4f8925414b8607d5/testing/buildbot/chromium.gpu.json
,
Dec 30 2016
The commit above switched these tests to run in the more robust gpu_integration_test harness, which has better support for flaky retries. I suspect this may fix the problem but regardless this step (gpu_rasterization_tests) will no longer run on the bots. Any flakes will show up in the pixel_test step. Closing as fixed.
,
Dec 30 2016
,
Dec 30 2016
Issue 675770 has been merged into this issue. |
||||
►
Sign in to add a comment |
||||
Comment 1 by henrika@chromium.org
, Dec 23 2016Labels: -Sheriff-Chromium
Owner: kbr@chromium.org