Roll ANGLE from a469a5d3f5c5 to e7418836e432 (5 revisions) https://chromium.googlesource.com/angle/angle.git/+log/a469a5d3f5c5..e7418836e432 2023-09-12 abdolrashidi@google.com Vulkan: Add context flushing as OOM fallback 2023-09-12 mark@lunarg.com Tests: Add Oxenfree trace 2023-09-12 m.maiya@samsung.com Vulkan: Perform CPU wait in clientWait outside the global lock 2023-09-12 syoussefi@chromium.org Vulkan: Add host-image-copy usage to images when optimal 2023-09-12 syoussefi@chromium.org Vulkan: Refactor image usage/flags support check logic If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/angle-chromium-autoroll Please CC angle-team@google.com,ianelliott@google.com on the revert to ensure that a human is aware of the problem. To file a bug in ANGLE: https://bugs.chromium.org/p/angleproject/issues/entry To file a bug in Chromium: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86 Bug: None Tbr: ianelliott@google.com Test: Test: angle_trace_tests --gtest_filter=TraceTest.oxenfree Change-Id: Icb52899bffaa046cac7caa5e12625f5c0998d69f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4861010 Commit-Queue: Shahbaz Youssefi <syoussefi@chromium.org> Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1195993}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.