"gpu_tests.context_lost_integration_test.ContextLostIntegrationTest.ContextLost_WebGLContextLostFromSelectElement" is flaky |
||||
Issue description"gpu_tests.context_lost_integration_test.ContextLostIntegrationTest.ContextLost_WebGLContextLostFromSelectElement" 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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyewsSBUZsYWtlInBncHVfdGVzdHMuY29udGV4dF9sb3N0X2ludGVncmF0aW9uX3Rlc3QuQ29udGV4dExvc3RJbnRlZ3JhdGlvblRlc3QuQ29udGV4dExvc3RfV2ViR0xDb250ZXh0TG9zdEZyb21TZWxlY3RFbGVtZW50DA. 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
,
Jun 29 2018
Assigning bug to kbr@ who looks to be owner of this code. Created crosreview.com/1119622 for this to mark WebGLContextLostFromWelectElement and WebGLContextLostFromQuantity as flaky. I'm going to let it run on the bots before submitting since I'm not familiar at all with these tests and how exactly to mark flaky tests.
,
Jun 29 2018
Presubmit is failing on my patch to mark these tests as flaky. kbr@, feel free to take over this CL. I clearly don't know what I'm doing :) It looks like these tests have been passing OK since the 3 reported failures, so I will reduce priority.
,
Jun 29 2018
In duplicate Issue 858873 gpu_tests.context_lost_integration_test.ContextLostIntegrationTest.ContextLost_WebGLContextLostFromQuantity was also reported flaky: https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNydgsSBUZsYWtlImtncHVfdGVzdHMuY29udGV4dF9sb3N0X2ludGVncmF0aW9uX3Rlc3QuQ29udGV4dExvc3RJbnRlZ3JhdGlvblRlc3QuQ29udGV4dExvc3RfV2ViR0xDb250ZXh0TG9zdEZyb21RdWFudGl0eQw There were exactly 3 flakes of both of these tests: https://ci.chromium.org/p/chromium/builders/luci.chromium.try/android-marshmallow-arm64-rel/28143 https://ci.chromium.org/p/chromium/builders/luci.chromium.try/android-marshmallow-arm64-rel/28072 https://ci.chromium.org/p/chromium/builders/luci.chromium.try/android-marshmallow-arm64-rel/27743 and they all had the same symptom: - chrome_public_test_apk failed all of its shards - These two context_lost tests failed with timeouts See the following example shard of chrome_public_test_apk: https://chromium-swarm.appspot.com/task?id=3e609bfe7a118e10&refresh=10&show_raw=1 and this one for context_lost_tests: https://chromium-swarm.appspot.com/task?id=3e609c9554a38b10&refresh=10&show_raw=1 In the logs for chrome_public_test_apk, the following was output: E 159.752s list_tests(00f25e2ac4610ec1) Unexpected output while listing tests: E 159.752s list_tests(00f25e2ac4610ec1) INSTRUMENTATION_RESULT: shortMsg=java.lang.NoClassDefFoundError E 159.752s list_tests(00f25e2ac4610ec1) INSTRUMENTATION_RESULT: longMsg=java.lang.NoClassDefFoundError: net.bytebuddy.agent.builder.ResettableClassFileTransformer E 159.752s list_tests(00f25e2ac4610ec1) INSTRUMENTATION_CODE: 0 Essentially: I think something was broken in Chrome on Android when these three tryjobs ran, and that the binaries that ran on the devices were busted. It seems that whatever was broken has since recovered. I don't think we should take any action like marking these tests flaky in response. Closing as WontFix. |
||||
►
Sign in to add a comment |
||||
Comment 1 by joelhockey@chromium.org
, Jun 29 2018