Open Bug 1968576 Opened 1 year ago Updated 4 days ago

perma fail ubuntu 24.04 debug socketprocess-networking: browser/components/asrouter/tests/browser/browser_feature_callout_in_chrome.js

Categories

(Firefox :: Messaging System, defect, P2)

defect

Tracking

()

REOPENED

People

(Reporter: jmaher, Unassigned, NeedInfo)

References

Details

when running tests in CI on a newer version of linux (18.04 -> 24.04) we run into some new perma failures.

in this debug log, you can see this failure:

[task 2025-05-24T20:20:37.703Z] 20:20:37     INFO - TEST-INFO | Main app process: exit 0
[task 2025-05-24T20:20:37.703Z] 20:20:37     INFO - TEST-INFO | Confirming we saw 315 DOCSHELL created and 315 destroyed log strings.
[task 2025-05-24T20:20:37.704Z] 20:20:37     INFO - TEST-INFO | Confirming we saw 816 DOMWINDOW created and 816 destroyed log strings.
[task 2025-05-24T20:20:37.704Z] 20:20:37     INFO - TEST-INFO | browser/components/asrouter/tests/browser/browser_feature_callout_in_chrome.js | windows(s) leaked: [pid = 2148] [serial = 183], [pid = 2148] [serial = 182]
[task 2025-05-24T20:20:37.705Z] 20:20:37     INFO - TEST-UNEXPECTED-FAIL | browser/components/asrouter/tests/browser/browser_feature_callout_in_chrome.js | leaked 1 window(s) until shutdown [url = about:blank]
[task 2025-05-24T20:20:37.705Z] 20:20:37     INFO - TEST-INFO 
[task 2025-05-24T20:20:37.705Z] 20:20:37     INFO - TEST-UNEXPECTED-FAIL | browser/components/asrouter/tests/browser/browser_feature_callout_in_chrome.js | leaked 1 window(s) until shutdown [url = chrome://browser/content/browser.xhtml]

this bug will be for tracking investigations, I will be skipping these tests in a manifest in a larger patch to green stuff up.

Joel, are you going to be investigating this or would you like it assigned to someone from messaging system?

Flags: needinfo?(jmaher)

I am not looking into this, I am only filing issues and skipping tests in order to upgrade our linux systems in CI.

Flags: needinfo?(jmaher)
Depends on: 1969523

This test is being skipped for now in bug 1969523. This could possibly be due to upgrades to the Linux systems.

Priority: -- → P2

The severity field is not set for this bug.
:aminomancer, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(shughes)
Status: NEW → RESOLVED
Closed: 17 days ago
Flags: needinfo?(shughes)
Resolution: --- → WORKSFORME
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---

The severity field is not set for this bug.
:sachung, could you have a look please?

For more information, please visit BugBot documentation.

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