Closed Bug 1752090 Opened 3 years ago Closed 3 years ago

comm-central perm fail after bug 1748524 - toolkit/components/extensions/test/xpcshell/test_ext_eventpage_warning.js | test_eventpages - [test_eventpages : 1732] Did not get expected console message: ({message:/Event pages are not currently supported./})

Categories

(Thunderbird :: Add-Ons: Extensions API, defect, P5)

Tracking

(thunderbird_esr91 unaffected)

RESOLVED FIXED
98 Branch
Tracking Status
thunderbird_esr91 --- unaffected

People

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

References

(Regression)

Details

(Keywords: intermittent-failure, regression)

Attachments

(1 file, 1 obsolete file)

Filed by: geoff [at] darktrojan.net
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=365472782&repo=comm-central
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/CRQC085hTwyOcLwoC8BNgQ/runs/0/artifacts/public/logs/live_backing.log


Backing out https://hg.mozilla.org/mozilla-central/rev/bee5e1a1f2013c73bfc93fdc067f6407d0c5b180 makes it go away.
Summary: Permanent toolkit/components/extensions/test/xpcshell/test_ext_eventpage_warning.js | test_eventpages - [test_eventpages : 1732] Did not get expected console message: ({message:/Event pages are not currently supported./}) - false == true → comm-central perm fail after bug 1748524 - toolkit/components/extensions/test/xpcshell/test_ext_eventpage_warning.js | test_eventpages - [test_eventpages : 1732] Did not get expected console message: ({message:/Event pages are not currently supported./})

John, can you take this one

Flags: needinfo?(john)
Assignee: nobody → john
Flags: needinfo?(john)

This has to be added to the test because we have a different default:

Services.prefs.setBoolPref(
  "extensions.webextensions.background-delayed-startup",
  true
);

Could we switch the default for Daily and see what happens? I do not really know what that pref is doing or how much it is delaying startup.

That pref should be false in general for xpcshell tests, but true otherwise. Unfortunately libpref/init/all.js has it set to false. This pref will eventually die, it's problematic for work we're doing right now.

@Shane: Do I read you correctly, that we should not switch Thunderbird to use background-delayed-startup set to true, as it will go away and then it will behave like having that pref set to false again?

So the way forward is to file a bug against mozilla-central and set the pref to true to make the test pass on comm-central and mozilla-central?

The way we usually do this (it's bug 1168178 again), just change the test to make the test set the pref it in reality needs. Then at follows along whatever work is getting done on it...

Status: NEW → ASSIGNED

(In reply to John Bieling (:TbSync) from comment #5)

@Shane: Do I read you correctly, that we should not switch Thunderbird to use background-delayed-startup set to true, as it will go away and then it will behave like having that pref set to false again?

No, exactly the opposite. TB should set it to true, otherwise when we remove the pref, TB will be forced to true, and you wont have found any issues you might have.

The pref should only be set to false in a test if you are entirely certain it is ok to. Ultimately all those tests will have to be fixed.

So the way forward is to file a bug against mozilla-central and set the pref to true to make the test pass on comm-central and mozilla-central?

m-c doesn't need that. And rather than editing a single test, you should set it to true in comm-central for TB like it is for firefox.

https://searchfox.org/mozilla-central/rev/78963fe42f8d5f582f84da84a5e78377b6c1fc32/browser/app/profile/firefox.js#67

Thanks for the clarification, Shane.

Could you give a few details what that pref is actually doing? Until what point during startup will the execution of background scripts be delayed? Is there any documentation I could read to learn more about it and its consequences?

(In reply to Shane Caraveo (:mixedpuppy) from comment #11)

So the way forward is to file a bug against mozilla-central and set the pref to true to make the test pass on comm-central and mozilla-central?

m-c doesn't need that. And rather than editing a single test, you should set it to true in comm-central for TB like it is for firefox.

Well, "need" is relative. m-c needs it addressed before you finally remove the pref altogether, since the test needs it. It's just that you don't notice it at the moment due to bug 1168178.

Actually, I'm confused now. Isn't it the case that it works only with false atm?

(In reply to Magnus Melin [:mkmelin] from comment #14)

Actually, I'm confused now. Isn't it the case that it works only with false atm?

It needs true to pass. I verified with building Firefox locally with my patch. But it looks like we should switch the pref for us and see how bad we get burned and clean up.

Edit: But I sure would like to understand what that pref actually does :-)

Attachment #9260943 - Attachment is obsolete: true

So it looks like we do not get burned:
https://treeherder.mozilla.org/jobs?repo=try-comm-central&revision=72a8cda932f4d075febfca74dff997726c6a67bb

There are a few tests failing, but I believe those to be not new.

Target Milestone: --- → 98 Branch
Target Milestone: 98 Branch → ---
Target Milestone: --- → 98 Branch

Pushed by mkmelin@iki.fi:
https://hg.mozilla.org/comm-central/rev/afa904374ea2
Enable extensions.webextensions.background-delayed-startup. r=mkmelin

Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Regressions: 1753392
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: