| commit | bee9ae94e99df609a0eb3b4aaae932e17cfef9e4 | [log] [tgz] |
|---|---|---|
| author | Jonathan Lee <jonathanjlee@google.com> | Wed Dec 11 18:01:41 2024 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Dec 11 18:01:41 2024 |
| tree | 44fdf69e8dafe71037600b00645fdf8641a291f6 | |
| parent | a390a91c061706053e86331fc6042c91b1a4ef67 [diff] |
[wptrunner] Remove obsolete `XDG_CONFIG_HOME` creation In https://crrev.com/c/5882842, `run_wpt_tests.py` sets up a temporary `XDG_CONFIG_HOME` so that `headless_shell` or `chrome` discovers test fonts on Linux (`content_shell` has magic test code to do this). However, when showing the test results after an interactive run, the browser spawned would inherit the test-only `XDG_CONFIG_HOME` variable. Chromium treats that as a user data directory with no profiles [0], causing the first-run UI to always run. Just delete the `XDG_CONFIG_HOME` workaround, since it's been recently superseded by https://crrev.com/c/6079445. Related drive-by: `os.environ` -> `host.environ`, which are the same in production but the latter is a fake in tests. [0]: https://chromium.googlesource.com/chromium/src/+/main/docs/user_data_dir.md Bug: 381127663 Change-Id: I7df71c1869675406a2c170e4de20895771589195 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6086798 Commit-Queue: Jonathan Lee <jonathanjlee@google.com> Reviewed-by: Weizhong Xia <weizhong@google.com> Cr-Commit-Position: refs/heads/main@{#1394922}
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.