[gtest] Consume `AssertionResult`s in `//c/c/extensions/permissions/` Wrap each `testing::AssertionResult` in an `EXPECT_TRUE(...)` [0] to actually check if the assertion passed. The dropped assertion causes a build failure [1] with a recent Googletest revision that marks `AssertionResult` as `[[nodiscard]]` [2]. [0]: https://google.github.io/googletest/advanced.html#predicate-assertions-for-better-error-messages [1]: https://ci.chromium.org/ui/p/chromium/builders/try/linux-rel/2130794/overview [2]: https://chromium.googlesource.com/external/github.com/google/googletest.git/+/3fbe4db9a39291ae8d7a9c5f1d75896bb4c5a18f%5E%21/ Bug: 398298306 Change-Id: If6b96b50b426cf7ff76e41d4ca2ac28e53d03f3b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6303081 Reviewed-by: David Bertoni <dbertoni@chromium.org> Commit-Queue: Jonathan Lee <jonathanjlee@google.com> Cr-Commit-Position: refs/heads/main@{#1425193}
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.