Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/946e3173ce19c18e805b4fbb2218cb7149429793 (Do LOG(FATAL) if layout tests fall out of gpu compositing.).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.

 Issue 780757  has been merged into this issue.

All context for this is in https://bugs.chromium.org/p/chromium/issues/detail?id=780757

Need to make these bots use --use-gl=swiftshader to allow gpu compositing to work. Currently it doesn't work on the bots, which is a pre-req for layout tests.

I applied the following changes:

1)
APP_ARGS: --use-gl=osmesa  ->  --use-gl=swiftshader
REQUIRED_APP_ARGS: --use-gl=any  ->  --use-gl=swiftshader

for the following job template:
- linux_asan_chrome


2)
APP_ARGS: --use-gl=any  ->  --use-gl=swiftshader
REQUIRED_APP_ARGS: --use-gl=any  ->  --use-gl=swiftshader


for the following job types:
- linux_asan_chrome_ipc
- linux_asan_chrome_ipc_32bit
- linux_asan_chrome_v8_arm
- linux_asan_content_shell
- linux_asan_content_shell_drt
- linux_cfi_chrome
- linux_asan_flash_disabled
- linux_cfi_chrome_ipc
- linux_debug_chrome
- linux_debug_content_shell_drt
- linux_lsan_chrome_mp
- linux_msan_chrome_ipc
- linux_official_chrome_disabled
- linux_ubsan_chrome
- linux_ubsan_vptr_chrome
- linux_ubsan_vptr_content_shell_drt
- windows_asan_chrome
- windows_asan_chrome_ipc
- windows_asan_chrome_no_sandbox
- windows_asan_content_shell
- windows_official_chrome_disabled
- windows_syzyasan_chrome
- windows_syzyasan_content_shell

ClusterFuzz is analyzing your testcase. Developers can follow the progress at https://clusterfuzz.com/testcase?key=5132173744275456.

Re-uploaded the same input against the same job type: https://clusterfuzz.com/v2/testcase-detail/5132173744275456

Alright, it didn't crash with --use-gl=swiftshader flag.

Cool, thanks. :)

ClusterFuzz testcase 5241963845779456 is still reproducing on tip-of-tree build (trunk).

Please re-test your fix against this testcase and if the fix was incorrect or incomplete, please re-open the bug. Otherwise, ignore this notification and add ClusterFuzz-Wrong label.

CF thinks that it's still reproducible, as it tried to reproduce the issue with the same arguments as it was found. Let me try to change the arguments for this particular testcase, then it should go away.

Yup, updated the arguments manually and now CF cannot reproduce that anymore, as expected. Closing again.