Fix incremental progress bar in run_web_tests. By default (no --verbose or --debug-rwt-logging), run_web_tests is supposed to show a ninja-style incremental progress bar while running (i.e., it prints "[1/10000] foo/bar.html" and overwrites that line as we progress through the tests). The line is printed to stderr, and in Python 2, stderr is unbuffered, meaning that lines are immediately flushed and printed. In Python 3, stderr changed to being buffered, meaning that non of the updates get printed until something else needs to be printed (like a test failure, or the completion of the tests). Which defeats the point. This CL explicitly calls out to flush stderr after printing the progress update. Change-Id: Ia7f1c97b9d514982cae1fa06613d2dbd72c254ce Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5972803 Commit-Queue: Dirk Pranke <dpranke@google.com> Reviewed-by: Weizhong Xia <weizhong@google.com> Cr-Commit-Position: refs/heads/main@{#1375438}
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.