Closed Bug 1605722 Opened 1 year ago Closed 1 year ago

Enable target discovery by default for browser chrome tests

Categories

(Remote Protocol :: Agent, task, P1)

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.

Summary: Workaround for hangs when waiting for the `Target.activateTarget` event in browser chrome tests → Enable target discovery by default for browser chrome tests
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
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 73
You need to log in before you can comment on or make changes to this bug.