commit | 804b5ce2c1e76ee5eb90eab28cf1bdcc8e2532b9 | [log] [tgz] |
---|---|---|
author | Jonathan Lee <jonathanjlee@google.com> | Mon Mar 24 17:32:44 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Mar 24 17:32:44 2025 |
tree | f1bc924e44d92935e68c094f2ec98469eac92752 | |
parent | 7b92d784626e38782133db092ef396b43369cb75 [diff] |
[upf] Parse internal `b/` bugs from expectations Internal bugs are discouraged but make sense in a few cases (e.g., b/267953710, [0], security-related), so the UPF should comment on them too instead of crashing [1]. Buganizer IDs are globally unique across trackers, so the number after `b/` can be used as-is. [0]: https://source.chromium.org/search?q=%5Eb%2F%20f:exp&sq= [1]: https://logs.chromium.org/logs/chrome/buildbucket/cr-buildbucket/8719898266927616849/+/u/remove_stale_blink_expectations/run_script/stdout Bug: 41491345 Test: PYTHONPATH=${PWD}:${PYTHONPATH} ./unexpected_passes_common/result_output_unittest.py Change-Id: Ia1e646e7f774dbe21b6f9d558313a966c3e8a774 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6384040 Auto-Submit: Jonathan Lee <jonathanjlee@google.com> Reviewed-by: Brian Sheedy <bsheedy@chromium.org> Commit-Queue: Jonathan Lee <jonathanjlee@google.com> Commit-Queue: Brian Sheedy <bsheedy@chromium.org> Cr-Commit-Position: refs/heads/main@{#1436949}
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.