Closed
Bug 1424369
Opened 7 years ago
Closed 6 years ago
Run webdriver Rust tests
Categories
(Testing :: geckodriver, enhancement)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: ato, Unassigned)
Details
https://bugzil.la/1395933 used to track running both geckodriver and webdriver Rust unit tests on try, but the webdriver part of it has been split out to this bug. mach expects every Rust library that you want to run tests for through the RustTest directive to be a separately vendored crate. However, webdriver is only picked up as a path dependency to testing/geckodriver and does consequently not have its own Cargo.lock file. mach will complain about this if you try to build it: > % ./mach build testing/webdriver/check > 0:00.47 /usr/bin/make -C /home/ato/src/gecko/obj-x86_64-pc-linux-gnu -j90 -s backend > 0:00.55 /usr/bin/make -C testing/webdriver -j90 -s check > 0:00.84 [m[m[31m[1merror:[m the lock file needs to be updated but --frozen was passed to prevent this > 0:00.84 /home/ato/src/gecko/config/rules.mk:973: recipe for target 'force-cargo-test-run' failed > 0:00.84 make: *** [force-cargo-test-run] Error 101
Reporter | ||
Comment 1•6 years ago
|
||
This was resolved by other work. Don’t have the time to dig up the bug references right now.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•