Closed
Bug 1855159
Opened 9 months ago
Closed 9 months ago
Use geckodriver in target directory if it exists
Categories
(Testing :: web-platform-tests, enhancement)
Testing
web-platform-tests
Tracking
(firefox120 fixed)
RESOLVED
FIXED
120 Branch
| Tracking | Status | |
|---|---|---|
| firefox120 | --- | fixed |
People
(Reporter: jgraham, Assigned: jgraham)
References
Details
Attachments
(1 file)
Since this is what you get in the case you do an artifact build of firefox and a local build of geckodriver.
|
Assignee | |
Comment 1•9 months ago
|
||
This is helpful if you use an artifact firefox build with a local geckodriver build.
|
||
Updated•9 months ago
|
Assignee: nobody → james
Status: NEW → ASSIGNED
|
||
Comment 2•9 months ago
|
||
See also bug 1640199 where we actually want to download geckodriver in case of artifact builds and no local build present.
See Also: → 1640199
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/autoland/rev/822139c4a9a5 Try to find geckodriver in cargo target directory, r=whimboo
|
||
Comment 4•9 months ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 9 months ago
status-firefox120:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 120 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•