tor-browser

The Tor Browser
git clone https://git.dasho.dev/tor-browser.git
Log | Files | Refs | README | LICENSE

commit 1d9941da4f73630b88029aeb34338cf9a2ee56e3
parent 7dcf806634b588166e771326567593a3e794b84e
Author: Erich Gubler <erichdongubler@gmail.com>
Date:   Wed, 17 Dec 2025 19:38:04 +0000

Bug 1942430 - chore(webgpu): hoist and refine patch file justification commentary in CTS `moz.yaml` r=webgpu-reviewers,teoxoy

We're going to add in a subsequent patch in the stack, so it's better to keep the common rationale for them above.

Differential Revision: https://phabricator.services.mozilla.com/D275670

Diffstat:
Mdom/webgpu/tests/cts/moz.yaml | 12+++++++-----
1 file changed, 7 insertions(+), 5 deletions(-)

diff --git a/dom/webgpu/tests/cts/moz.yaml b/dom/webgpu/tests/cts/moz.yaml @@ -40,13 +40,15 @@ vendoring: pattern: "const { version } = require('../src/common/tools/version.ts');" with: "const version = '{revision}';" + # Apply patches from patch files. + # + # These must be applied prior to the `cargo run` step below, as it patches the original + # TypeScript sources. If we used `moz.yaml`'s `patches` mechanism, it would apply the patch to + # the TypeScript sources _after_ we have already processed them and written our tests to their + # final location. + # Patch the `baseResourcePath` used by the CTS so that the tests we # generate are able to load resources correctly. - # This must be invoked as a run-command prior to the `cargo run` step - # below, as it patches the original typescript sources. If we used - # moz.yaml's `patches` mechanism it would apply the patch to the typescript - # sources after we have already processed them and written our tests to - # their final location. - action: run-command cwd: '{yaml_dir}/checkout/' command: patch