1789188 - Intermittent browser/components/tests/browser/browser_browserGlue_upgradeDialog_trigger.js | Test timed out -

Status: RESOLVED DUPLICATE of bug 1789186

(Firefox :: General, defect, P2)

Description

[Treeherder Bug Filer]

Filed by: ccozmuta [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=389470817&repo=autoland
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/NUwyh8zzTcWq9u-Iad0eHg/runs/0/artifacts/public/logs/live_backing.log
Reftest URL: https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/NUwyh8zzTcWq9u-Iad0eHg/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1

---

[task 2022-09-05T05:00:57.134Z] 05:00:57     INFO - TEST-PASS | browser/components/tests/browser/browser_browserGlue_upgradeDialog_trigger.js | parent must be in snapshot. Has [parent]. - true == true - 
[task 2022-09-05T05:00:57.134Z] 05:00:57     INFO - TEST-PASS | browser/components/tests/browser/browser_browserGlue_upgradeDialog_trigger.js | After filtering we must have the expected number of events. - 1 == 1 - 
[task 2022-09-05T05:00:57.135Z] 05:00:57     INFO - TEST-PASS | browser/components/tests/browser/browser_browserGlue_upgradeDialog_trigger.js | category in event upgrade_dialog#trigger#reason must match. - "upgrade_dialog" matches "upgrade_dialog" - 
[task 2022-09-05T05:00:57.135Z] 05:00:57     INFO - TEST-PASS | browser/components/tests/browser/browser_browserGlue_upgradeDialog_trigger.js | method in event upgrade_dialog#trigger#reason must match. - "trigger" matches "trigger" - 
[task 2022-09-05T05:00:57.136Z] 05:00:57     INFO - TEST-PASS | browser/components/tests/browser/browser_browserGlue_upgradeDialog_trigger.js | object in event upgrade_dialog#trigger#reason must match. - "reason" matches "reason" - 
[task 2022-09-05T05:00:57.137Z] 05:00:57     INFO - TEST-PASS | browser/components/tests/browser/browser_browserGlue_upgradeDialog_trigger.js | value in event upgrade_dialog#trigger#reason must match. - "no-welcome" matches "no-welcome" - 
[task 2022-09-05T05:00:57.137Z] 05:00:57     INFO - Leaving test bound enterprise_disabled
[task 2022-09-05T05:00:57.138Z] 05:00:57     INFO - Entering test bound show_major_upgrade
[task 2022-09-05T05:00:57.138Z] 05:00:57     INFO - Console message: [JavaScript Error: "formatURL: Couldn't find value for key: OLD_VERSION" {file: "resource://gre/modules/URLFormatter.jsm" line: 157}]
[task 2022-09-05T05:00:57.139Z] 05:00:57     INFO - replacementCallback@resource://gre/modules/URLFormatter.jsm:157:10
[task 2022-09-05T05:00:57.139Z] 05:00:57     INFO - uf_formatURL@resource://gre/modules/URLFormatter.jsm:160:20
[task 2022-09-05T05:00:57.139Z] 05:00:57     INFO - uf_formatURLPref@resource://gre/modules/URLFormatter.jsm:188:17
[task 2022-09-05T05:00:57.139Z] 05:00:57     INFO - getArgs@resource:///modules/BrowserContentHandler.jsm:701:50
[task 2022-09-05T05:00:57.139Z] 05:00:57     INFO - get defaultArgs@resource:///modules/BrowserContentHandler.jsm:648:17
[task 2022-09-05T05:00:57.139Z] 05:00:57     INFO - remote_disabled@chrome://mochitests/content/browser/browser/components/tests/browser/browser_browserGlue_upgradeDialog_trigger.js:41:36
[task 2022-09-05T05:00:57.139Z] 05:00:57     INFO - 
[task 2022-09-05T05:00:57.139Z] 05:00:57     INFO - Buffered messages logged at 05:00:13
[task 2022-09-05T05:00:57.140Z] 05:00:57     INFO - Global property added while loading chrome://browser/content/places/browserPlacesViews.js: PlacesViewBase
[task 2022-09-05T05:00:57.140Z] 05:00:57     INFO - Buffered messages finished
[task 2022-09-05T05:00:57.141Z] 05:00:57     INFO - TEST-UNEXPECTED-FAIL | browser/components/tests/browser/browser_browserGlue_upgradeDialog_trigger.js | Test timed out - 
[task 2022-09-05T05:00:57.141Z] 05:00:57     INFO - Not taking screenshot here: see the one that was previously logged
[task 2022-09-05T05:00:57.142Z] 05:00:57     INFO - TEST-UNEXPECTED-FAIL | browser/components/tests/browser/browser_browserGlue_upgradeDialog_trigger.js | Uncaught exception received from previously timed out test - subdialog-loaded observer not removed before the end of test
[task 2022-09-05T05:00:57.142Z] 05:00:57     INFO - Entering test bound dont_reshow
[task 2022-09-05T05:00:57.142Z] 05:00:57     INFO - Checking telemetry events: Shouldn't reshow for upgrade dialog requirements
[task 2022-09-05T05:00:57.143Z] 05:00:57     INFO - TEST-PASS | browser/components/tests/browser/browser_browserGlue_upgradeDialog_trigger.js | parent must be in snapshot. Has [parent]. - true == true - 
[task 2022-09-05T05:00:57.143Z] 05:00:57     INFO - Not taking screenshot here: see the one that was previously logged
[task 2022-09-05T05:00:57.144Z] 05:00:57     INFO - TEST-UNEXPECTED-FAIL | browser/components/tests/browser/browser_browserGlue_upgradeDialog_trigger.js | After filtering we must have the expected number of events. - 2 == 1 - JS frame :: resource://testing-common/TelemetryTestUtils.jsm :: assertEvents :: line 181
[task 2022-09-05T05:00:57.144Z] 05:00:57     INFO - Stack trace:
[task 2022-09-05T05:00:57.144Z] 05:00:57     INFO - resource://testing-common/TelemetryTestUtils.jsm:assertEvents:181
[task 2022-09-05T05:00:57.145Z] 05:00:57     INFO - chrome://mochitests/content/browser/browser/components/tests/browser/head.js:AssertEvents:18
[task 2022-09-05T05:00:57.145Z] 05:00:57     INFO - chrome://mochitests/content/browser/browser/components/tests/browser/browser_browserGlue_upgradeDialog_trigger.js:dont_reshow:95
[task 2022-09-05T05:00:57.145Z] 05:00:57     INFO - resource://testing-common/PromiseTestUtils.jsm:ensureDOMPromiseRejectionsProcessed:119
[task 2022-09-05T05:00:57.145Z] 05:00:57     INFO - chrome://mochikit/content/browser-test.js:nextTest:662
[task 2022-09-05T05:00:57.145Z] 05:00:57     INFO - TEST-PASS | browser/components/tests/browser/browser_browserGlue_upgradeDialog_trigger.js | category in event upgrade_dialog#trigger#reason must match. - "upgrade_dialog" matches "upgrade_dialog" - 
[task 2022-09-05T05:00:57.146Z] 05:00:57     INFO - TEST-PASS | browser/components/tests/browser/browser_browserGlue_upgradeDialog_trigger.js | method in event upgrade_dialog#trigger#reason must match. - "trigger" matches "trigger" - 
[task 2022-09-05T05:00:57.146Z] 05:00:57     INFO - TEST-PASS | browser/components/tests/browser/browser_browserGlue_upgradeDialog_trigger.js | object in event upgrade_dialog#trigger#reason must match. - "reason" matches "reason" - 
[task 2022-09-05T05:00:57.147Z] 05:00:57     INFO - Not taking screenshot here: see the one that was previously logged
[task 2022-09-05T05:00:57.147Z] 05:00:57     INFO - TEST-UNEXPECTED-FAIL | browser/components/tests/browser/browser_browserGlue_upgradeDialog_trigger.js | value in event upgrade_dialog#trigger#reason must match. - "satisfied" matches "already-shown" - JS frame :: resource://testing-common/TelemetryTestUtils.jsm :: assertEvents :: line 216
[task 2022-09-05T05:00:57.147Z] 05:00:57     INFO - Stack trace:
[task 2022-09-05T05:00:57.147Z] 05:00:57     INFO - resource://testing-common/TelemetryTestUtils.jsm:assertEvents:216
[task 2022-09-05T05:00:57.148Z] 05:00:57     INFO - chrome://mochitests/content/browser/browser/components/tests/browser/head.js:AssertEvents:18

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

:dmosedale, since you are the author of the regressor, bug 1789008, could you take a look?

For more information, please visit auto_nag documentation.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

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

Comment 3

[Dan Mosedale (:dmosedale, :dmose)]

I've got a fix for this locally.

Comment 4

[Dan Mosedale (:dmosedale, :dmose)]

Attachment: Bug 1789188 - Clear telemetry in upgradeDialog tests checking it, r?Mardak

Comment 5

[Dan Mosedale (:dmosedale, :dmose)]

Attachment: WIP: Bug 1789188 - Clear telemetry in upgradeDialog tests checking it

Comment 6

[Intermittent Failures Robot]

28 failures in 3616 pushes (0.008 failures/push) were associated with this bug in the last 7 days.

This is the #48 most frequent failure this week.

Repository breakdown:

• autoland: 22
• try: 3
• mozilla-central: 3

Platform and build breakdown:

• macosx1015-64-qr: 1
  • opt: 1
• linux1804-64-qr: 19
  • debug: 19
• linux1804-64-asan-qr: 7
  • opt: 7
• windows10-64-2004-asan-qr: 1
  • opt: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures/bugdetails?bug=1789188&startday=2022-09-05&endday=2022-09-11&tree=all

Comment 7

[Dan Mosedale (:dmosedale, :dmose)]

I suspect that the fix for bug 1789186 will fix this. Even if it doesn't I don't think this is a P1 for 106, so dropping it to P2.

Comment 8

[Intermittent Failures Robot]

19 failures in 3023 pushes (0.006 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• autoland: 16
• try: 1
• mozilla-central: 2

Platform and build breakdown:

• linux1804-64-qr: 14
  • debug: 14
• linux1804-64-asan-qr: 1
  • opt: 1
• macosx1015-64-qr: 2
  • debug: 1
  • opt: 1
• windows10-32-2004-qr: 1
  • debug: 1
• windows10-64-2004-qr: 1
  • debug: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures/bugdetails?bug=1789188&startday=2022-09-12&endday=2022-09-18&tree=all

Comment 9

[BugBot [:suhaib / :marco/ :calixte]]

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

Comment 10

[Dan Mosedale (:dmosedale, :dmose)]

I landed the fix for bug 1789186 last Tuesday (in 106 Nightly). I think there's a good chance it will have fixed this bug as well. The treeherder link above shows zero failures, starting last Wednesday.

I'm resetting the release status flag to ---, as we don't (yet?) have evidence that this is happening in 107.

Comment 11

[BugBot [:suhaib / :marco/ :calixte]]

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

Comment 12

[Dan Mosedale (:dmosedale, :dmose)]

suhaib, given comment 10, what's the right thing to do here? A similar thing happened in bug 1789187....

Comment 13

[Suhaib Mujahid [:suhaib]]

(In reply to Dan Mosedale (:dmosedale, :dmose) from comment #12)

suhaib, given comment 10, what's the right thing to do here? A similar thing happened in bug 1789187....

I think we could mark Fx107 as ? since we do not know whether Fx107 is affected, or not. Once we know, we could change it to unaffected or affected.

Comment 14

[Dan Mosedale (:dmosedale, :dmose)]

No recurrences since fix for bug 1789186 landed in 106; marking tracking flags appropriately and closing.