mirror of
https://github.com/servo/servo
synced 2026-04-26 01:25:32 +02:00
1133eb229a
All other browsers use a single configuration for their browser invocations on WPT. Servo historically had two: servo and servodriver. Now that we run WPT on Servo GitHub CI with Webdriver using the servodriver, we can align our configuration with theirs. The existing "servo" configuration is renamed to "servo_legacy" and "servodriver" is then renamed to "servo". This way, we preserve the "servo" product name as defined on wpt.fyi, but we do use its webdriver configuration. Since webdriver is not fully working yet for debugging purposes, we keep the "servo_legacy" configuration now. In the future, once the debugging story has improved, we can remove "servo_legacy". All in all, this ensures that both on local, Servo GitHub CI and on wpt.fyi we all use the exact same configuration. I tested this locally by running the following test: ``` ./mach test-wpt tests/wpt/tests/css/css-overflow/scrollbar-gutter-dynamic-004.html ``` This does times out with the servo binary and works with the servodriver binary. Running the servo_legacy configuration is done via the `--servo-legacy` flag: ``` ./mach test-wpt tests/wpt/mozilla/tests/mozilla/caption.html --servo-legacy ``` Fixes #40751 --------- Signed-off-by: Tim van der Lippe <tvanderlippe@gmail.com>
This directory contains various Python modules used to support servo development.
servo
servo-specific python code e.g. implementations of mach commands. This is the canonical repository for this code.
tidy
servo-tidy is used to check licenses, line lengths, whitespace, ruff on Python files, lock file versions, and more.
wpt
servo-wpt is a module with support scripts for running, importing, exporting, updating manifests, and updating expectations for WPT tests.