Deflake invalidation tracking trace event test The test was flaky because some events that are tested here are not dispatched for unknown reasons on some instances of the event execution. This CL aims to reduce flakiness by adding multiple attempts to the tracing + test scenario flow when the events that are needed aren't found. I took the opportunity to incorporate a flaky legacy devtools test into this test so that we can get rid of it. For this, the stack trace of the Layout event is checked to ensure it includes the function that caused the layout Bug: 1444416 Change-Id: Id2df32d2b291b689154b1576b33d84764f9b8aa4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4521104 Reviewed-by: Jaroslav Sevcik <jarin@chromium.org> Commit-Queue: Andres Olivares <andoli@chromium.org> Cr-Commit-Position: refs/heads/main@{#1142625}
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.