Issue metadata
Sign in to add a comment
|
"gpu_tests.pixel_integration_test.PixelIntegrationTest.Pixel_OffscreenCanvas2DResizeOnWorker" is flaky |
||||||||||||||||||||||||
Issue description"gpu_tests.pixel_integration_test.PixelIntegrationTest.Pixel_OffscreenCanvas2DResizeOnWorker" 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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyZgsSBUZsYWtlIltncHVfdGVzdHMucGl4ZWxfaW50ZWdyYXRpb25fdGVzdC5QaXhlbEludGVncmF0aW9uVGVzdC5QaXhlbF9PZmZzY3JlZW5DYW52YXMyRFJlc2l6ZU9uV29ya2VyDA. 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 This flaky test/step was previously tracked in issue 690663 .
,
May 15 2018
Hmmm... this seems to be a dupe of issue 840394 . Let me try to figure out how to disable the test via content/test/gpu/gpu_tests/pixel_expectations.py and then dupe against the other bug.
,
May 15 2018
,
May 15 2018
Actually - fserb@, could you PTAL and 1) help decide if duping is desirable (the callstack in #c1 here seems different from the callstack reported in issue 840394 ) and 2) mark the test as flaky in content/test/gpu/gpu_tests/pixel_expectations.py (I'd rather not do it myself, as I am not familiar with the desired format of the expectations + I am not sure if I should add a new expectations or reuse the one for issue 840394 ).
,
May 15 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by lukasza@chromium.org
, May 15 2018+pmonette@, because the logs [1] show the following callstack (although I admit I don't really know if this callstack is directly related to the test failure - the logs are a bit confusing to me): chrome!base::debug::BreakDebugger+0xc ... chrome!logging::LogMessage::~LogMessage+0x46d chrome!base::subtle::RefCountedThreadSafeBase::AddRef+0x52 chrome!base::internal::WeakPtrBase::WeakPtrBase+0x32 chrome!base::WeakPtrFactory<content::AudioOutputAuthorizationHandler const >::GetWeakPtr+0x2b chrome!ModuleDatabase::OnModuleLoad+0x7f chrome!ModuleEventSinkImpl::OnModuleEvent+0x1a3 chrome!mojom::ModuleEventSinkStubDispatch::Accept+0x98 [1] https://logs.chromium.org/v/?s=chromium%2Fbb%2Ftryserver.chromium.win%2Fwin7_chromium_rel_ng%2F166302%2F%2B%2Frecipes%2Fsteps%2Fpixel_test_on_NVIDIA_GPU_on_Windows__with_patch__on_Windows-10%2F0%2Fstdout