Use a lazy pref getter for checking "dom.sitepermsaddon-provider.enabled" pref from SitePermsAddonProvider.sys.mjs
Categories
(Toolkit :: Add-ons Manager, task)
Tracking
()
Tracking | Status | |
---|---|---|
firefox108 | --- | fixed |
People
(Reporter: rpl, Assigned: rpl)
References
Details
(Whiteboard: [addons-jira])
Attachments
(1 file)
As a followup to Bug 1794162, we may use a lazy pref getter for checking "dom.sitepermsaddon-provider.enabled" from the SitePermsAddonProvider
's isEnabled
getter.
Updated•2 years ago
|
Assignee | ||
Comment 1•2 years ago
|
||
Updated•2 years ago
|
Comment 3•2 years ago
|
||
Backed out for causing build bustages TestDoublyLinkedList.exe_syms.track
- Backout link
- Push with failures
- Failure Log
- Failure line: gmake[4]: *** [/builds/worker/checkouts/gecko/config/rules.mk:655: TestDoublyLinkedList.exe_syms.track] Error 1
Assignee | ||
Comment 4•2 years ago
|
||
(In reply to Cristian Tuns from comment #3)
Backed out for causing build bustages TestDoublyLinkedList.exe_syms.track
- Backout link
- Push with failures
- Failure Log
- Failure line: gmake[4]: *** [/builds/worker/checkouts/gecko/config/rules.mk:655: TestDoublyLinkedList.exe_syms.track] Error 1
I never say "never", but I can't see (at least not yet) how the patch landed (which has a small change only applied to an sys.mjs Js module: cea85f67c505) could trigger that build error.
Also it seems that in the job with the failure the build job has been retriggered and it didn't fail the second time:
Hi Cristian,
could it be a false positive? would you mind to double-check if that is the case?
could you reland the patch if it turns out to be a false positive or should I?
Comment 6•2 years ago
|
||
The patch is relanded, sorry for the inconvenience.
Assignee | ||
Comment 7•2 years ago
|
||
(In reply to Iulian Moraru from comment #6)
The patch is relanded, sorry for the inconvenience.
no worries, and thanks a lot for confirming it and relanding the patch!
Comment 8•2 years ago
|
||
bugherder |
Description
•