geckodriver no longer waits for application shutdown nor force kills the browser process
Categories
(Testing :: geckodriver, defect, P3)
Tracking
(firefox-esr78 unaffected, firefox89 unaffected, firefox90 unaffected, firefox91 fixed)
| Tracking | Status | |
|---|---|---|
| firefox-esr78 | --- | unaffected |
| firefox89 | --- | unaffected |
| firefox90 | --- | unaffected |
| firefox91 | --- | fixed |
People
(Reporter: whimboo, Assigned: jgraham)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 obsolete file)
If the WebDriver:NewSession command from Marionette doesn't create a new session and returns a session not created error, geckodriver tries to shutdown the browser by deleting the session instead of force-killing it. This is actually a regression from bug 1705770.
I'll have a look given that I have all the required patches locally to reproduce it with the upcoming webSocketUrl capability.
|
||
Comment 1•3 years ago
|
||
Set release status flags based on info from the regressing bug 1705770
|
Reporter | |
Comment 2•3 years ago
|
||
This fixes a regression as introduced by bug 1705770 that
causes geckodriver to no longer wait for the browser to
shutdown nor force killing it in case of shutdown issues
or with no session present.
|
|
Reporter | |
Updated•3 years ago
|
|
||
Updated•3 years ago
|
|
|
||
Updated•3 years ago
|
|
|
Reporter | |
Comment 3•3 years ago
|
||
It will actually be fixed by the patch from James as recently attached on bug 1443520.
|
|
Reporter | |
Updated•3 years ago
|
|
|
Reporter | |
Comment 4•3 years ago
|
||
Fixed by bug 1443520.
Description
•