Open Bug 1835458 Opened 1 year ago Updated 5 months ago

Intermittent browser/base/content/test/webrtc/browser_WebrtcGlobalInformation.js | After closing 13 PCs there are no more than the max closed (7) PeerConnection Ids for stats history. - Got 13, expected 7

Categories

(Core :: WebRTC, defect, P5)

defect

Tracking

()

ASSIGNED
Tracking Status
firefox-esr102 --- unaffected
firefox113 --- unaffected
firefox114 --- unaffected
firefox115 --- affected
firefox116 --- affected

People

(Reporter: intermittent-bug-filer, Assigned: ng)

References

(Regression)

Details

(Keywords: intermittent-failure, regression, test-verify-fail)

Attachments

(1 file)

:ng, since you are the author of the regressor, bug 1830790, could you take a look?

For more information, please visit BugBot documentation.

Flags: needinfo?(na-g)
Assignee: nobody → na-g
Status: NEW → ASSIGNED

Set release status flags based on info from the regressing bug 1830790

I landed a fix for this in Bug 1830790 when I re-landed it. I would like to land this as well which is a more nuanced fixed. The timeout may need to be adjusted further.

Set release status flags based on info from the regressing bug 1830790

There is an r+ patch which didn't land and no activity in this bug for 2 weeks.
:ng, could you have a look please?
If you still have some work to do, you can add an action "Plan Changes" in Phabricator.
For more information, please visit BugBot documentation.

Flags: needinfo?(na-g)
Flags: needinfo?(docfaraday)

I'll land this shortly.

Flags: needinfo?(docfaraday)
Flags: needinfo?(na-g)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: