commit | 8e28fe494471b5956d72489d7859b28bd822d30d | [log] [tgz] |
---|---|---|
author | Guido Urdaneta <[email protected]> | Tue Aug 18 07:20:27 2020 |
committer | Commit Bot <[email protected]> | Tue Aug 18 07:20:27 2020 |
tree | e16f9d021d753fec4faa3146043d7e021a4e9b1d | |
parent | 96283ce5eced5f916d17a07324f44f40ce05dbd8 [diff] |
Revert "Roll Dawn from 988f19e208bb to d95180deded1 (2 revisions)" This reverts commit 1203768f4d9dd10fe9cbf9e9004621933907b771. Reason for revert: Speculative revert. Suspect of causing failures. https://ci.chromium.org/p/chromium/builders/ci/linux-bfcache-rel/7587 Original change's description: > Roll Dawn from 988f19e208bb to d95180deded1 (2 revisions) > > https://dawn.googlesource.com/dawn.git/+log/988f19e208bb..d95180deded1 > > 2020-08-17 [email protected] Roll 4 dependencies > 2020-08-17 [email protected] D3D12: only lazy clear OutputAttachment textures with render target ops > > If this roll has caused a breakage, revert this CL and stop the roller > using the controls here: > https://autoroll.skia.org/r/dawn-chromium-autoroll > Please CC [email protected] on the revert to ensure that a human > is aware of the problem. > > 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/master/autoroll/README.md > > Cq-Include-Trybots: luci.chromium.try:dawn-linux-x64-deps-rel;luci.chromium.try:dawn-mac-x64-deps-rel;luci.chromium.try:dawn-win10-x64-deps-rel;luci.chromium.try:dawn-win10-x86-deps-rel > Bug: None > Tbr: [email protected] > Change-Id: Ibcb597d53a688ed40d98a8496d24123e219d915f > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2360962 > Reviewed-by: chromium-autoroll <[email protected]> > Commit-Queue: chromium-autoroll <[email protected]> > Cr-Commit-Position: refs/heads/master@{#798975} [email protected],[email protected] Change-Id: I6cce941901be523a6faaaa915b8174614d794fa6 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: None Cq-Include-Trybots: luci.chromium.try:dawn-linux-x64-deps-rel;luci.chromium.try:dawn-mac-x64-deps-rel;luci.chromium.try:dawn-win10-x64-deps-rel;luci.chromium.try:dawn-win10-x86-deps-rel Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2362022 Reviewed-by: Guido Urdaneta <[email protected]> Commit-Queue: Guido Urdaneta <[email protected]> Cr-Commit-Position: refs/heads/master@{#799017}
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.
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.