Closed
Bug 1605722
Opened 4 years ago
Closed 4 years ago
Enable target discovery by default for browser chrome tests
Categories
(Remote Protocol :: Agent, task, P1)
Remote Protocol
Agent
Tracking
(firefox73 fixed)
RESOLVED
FIXED
Firefox 73
| Tracking | Status | |
|---|---|---|
| firefox73 | --- | fixed |
People
(Reporter: whimboo, Assigned: whimboo)
References
Details
(Keywords: hang)
Attachments
(1 file)
As agreed with Andreas we want to workaround bug 1605720 by moving the call to Target.setDiscoverTargets() into head.js so that each and every test, which is interacting with targets, doesn't face the hangs when waiting for eg. the Target.activateTarget() event.
|
Assignee | |
Comment 1•4 years ago
|
||
|
|
Assignee | |
Updated•4 years ago
|
Summary: Workaround for hangs when waiting for the `Target.activateTarget` event in browser chrome tests → Enable target discovery by default for browser chrome tests
|
||
Updated•4 years ago
|
Attachment #9117600 -
Attachment description: Bug 1605722 - [remote] Workaround for hangs when waiting for the `Target.activateTarget` event in browser chrome tests. r=#remote! → Bug 1605722 - [remote] Enable target discovery by default for browser chrome tests. r=#remote!
Pushed by hskupin@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/f49bf9b58686 [remote] Enable target discovery by default for browser chrome tests. r=remote-protocol-reviewers,ato
|
||
Comment 3•4 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox73:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 73
You need to log in
before you can comment on or make changes to this bug.
Description
•