Closed Bug 1370439 Opened 7 years ago Closed 7 years ago

Permaorange in browser_basic_rebuild_fonts_test.js when Gecko 55 merges to beta on 2017-06-12

Categories

(Firefox :: Settings UI, enhancement, P1)

55 Branch
enhancement

Tracking

()

RESOLVED FIXED
Firefox 55
Tracking Status
firefox-esr45 --- unaffected
firefox-esr52 --- unaffected
firefox53 --- unaffected
firefox54 --- unaffected
firefox55 blocking fixed

People

(Reporter: philor, Assigned: timdream)

References

Details

(Whiteboard: [photon-preference])

Attachments

(1 file)

Something that landed in the last week is going to cause https://treeherder.mozilla.org/logviewer.html#?job_id=104745546&repo=try when we merge to beta next week. [Tracking Requested - why for this release]: merge bustage, closed tree, delayed b1
marking as blocker for 55, this needs to be addressed before we ship 55.0beta
jaws, is there someone who can take a look?
Flags: needinfo?(jaws)
Ricky, can you look in to this?
Flags: needinfo?(jaws) → needinfo?(rchien)
FYI, this is currently marked as blocking Monday's merge of 55 to Beta.
Appearently all tests in in-content-new are run with old pref when it reaches beta...
Assignee: nobody → timdream
Blocks: 1363850
Status: NEW → ASSIGNED
Flags: needinfo?(rchien)
Priority: -- → P1
Whiteboard: [photon-preference]
Comment on attachment 8876007 [details] Bug 1370439 - Make sure new preferences page tests are running on the new preferences, https://reviewboard.mozilla.org/r/147446/#review151872 Yes, this makes sense. Thanks!
Attachment #8876007 - Flags: review?(jaws) → review+
Pushed by jwein@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/ca350cb8a959 Make sure new preferences page tests are running on the new preferences, r=jaws
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 55
Flags: qe-verify?
Flags: qe-verify? → qe-verify-
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: