Issue metadata
Sign in to add a comment
|
"SitePerProcessHitTestDataGenerationBrowserTest.ClippedOOPIFFastPath/1" is flaky |
||||||||||||||||||||||||
Issue description"SitePerProcessHitTestDataGenerationBrowserTest.ClippedOOPIFFastPath/1" 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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyUAsSBUZsYWtlIkVTaXRlUGVyUHJvY2Vzc0hpdFRlc3REYXRhR2VuZXJhdGlvbkJyb3dzZXJUZXN0LkNsaXBwZWRPT1BJRkZhc3RQYXRoLzEM. 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
,
Jul 30
Hi Ria, can you please take a look? I see you touched some other tests in this file recently so maybe you could take a look at this one too, or assign to a more appropriate person. Thanks. Error stack: [ RUN ] SitePerProcessHitTestDataGenerationBrowserTest.ClippedOOPIFFastPath/1 Xlib: extension "RANDR" missing on display ":99". DevTools listening on ws://127.0.0.1:38837/devtools/browser/37f0a299-4f62-4b6d-942a-0454892c6b2c [9021:9021:0727/101736.735452:FATAL:site_per_process_hit_test_browsertest.cc(4623)] Check failed: hit_test_data.size() >= 3. #0 0x000005f216f1 (/b/s/w/ir/out/Release/content_browsertests+0x5f216f0) #1 0x000010ba4b5c (/b/s/w/ir/out/Release/content_browsertests+0x10ba4b5b) #2 0x00001093ce03 (/b/s/w/ir/out/Release/content_browsertests+0x1093ce02) #3 0x000007322218 (/b/s/w/ir/out/Release/content_browsertests+0x7322217) #4 0x00000fa773c6 (/b/s/w/ir/out/Release/content_browsertests+0xfa773c5) #5 0x00000fd3395d (/b/s/w/ir/out/Release/content_browsertests+0xfd3395c) #6 0x00000d9048c5 (/b/s/w/ir/out/Release/content_browsertests+0xd9048c4) #7 0x00000eb4eb2c (/b/s/w/ir/out/Release/content_browsertests+0xeb4eb2b) #8 0x00000d90044c (/b/s/w/ir/out/Release/content_browsertests+0xd90044b) #9 0x00000d90dae7 (/b/s/w/ir/out/Release/content_browsertests+0xd90dae6) #10 0x00000fd31e53 (/b/s/w/ir/out/Release/content_browsertests+0xfd31e52) #11 0x00000fc1ffdf (/b/s/w/ir/out/Release/content_browsertests+0xfc1ffde) #12 0x00000d52baa2 (/b/s/w/ir/out/Release/content_browsertests+0xd52baa1) #13 0x000015560015 (/b/s/w/ir/out/Release/content_browsertests+0x15560014) #14 0x00000a849760 (/b/s/w/ir/out/Release/content_browsertests+0xa84975f) #15 0x00000fa75ec2 (/b/s/w/ir/out/Release/content_browsertests+0xfa75ec1) #16 0x00000fa4e37d (/b/s/w/ir/out/Release/content_browsertests+0xfa4e37c) #17 0x0000098685f3 (/b/s/w/ir/out/Release/content_browsertests+0x98685f2) #18 0x00000986a9b5 (/b/s/w/ir/out/Release/content_browsertests+0x986a9b4) #19 0x00000986bdc7 (/b/s/w/ir/out/Release/content_browsertests+0x986bdc6) #20 0x000009891af7 (/b/s/w/ir/out/Release/content_browsertests+0x9891af6) #21 0x000009890d23 (/b/s/w/ir/out/Release/content_browsertests+0x9890d22) #22 0x00000fb84a48 (/b/s/w/ir/out/Release/content_browsertests+0xfb84a47) #23 0x00000fa5c446 (/b/s/w/ir/out/Release/content_browsertests+0xfa5c445) #24 0x00000faf3668 (/b/s/w/ir/out/Release/content_browsertests+0xfaf3667) #25 0x00000fa5c2b4 (/b/s/w/ir/out/Release/content_browsertests+0xfa5c2b3) #26 0x7f069e802f45 (/lib/x86_64-linux-gnu/libc-2.19.so+0x21f44) #27 0x000005ed402a (/b/s/w/ir/out/Release/content_browsertests+0x5ed4029)
,
Aug 2
re-assign to sunxd@ who added this test case sunxd@, could you please take a look? Thanks
,
Aug 2
Another hit test browser test failed on asan, I'm merging this one. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by tikuta@chromium.org
, Jul 30