Closed Bug 1370890 Opened 3 years ago Closed 3 years ago
Upgrade Firefox 56 to NSS 3
Tracking NSS 3.32 for Firefox 56.
Because bug 1367435 isn't yet fixed, we must manually reset the files related to the automatic ABI checks.
Attachment #8875288 - Flags: review?(franziskuskiefer)
Attachment #8875288 - Flags: review?(franziskuskiefer) → review+
Assignee: nobody → franziskuskiefer
Comment on attachment 8875288 [details] [diff] [review] reset-abi-3.32.patch Ideally I should have used a bug for the NSS component, because this is a NSS-only commit... https://hg.mozilla.org/projects/nss/rev/2bbdb200520c
Attachment #8875288 - Flags: checkin+
Pushed by email@example.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/81a2b945dd16 land NSS a1a6eb781dd4 UPGRADE_NSS_RELEASE, r=me
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/mozilla-inbound/rev/79057bf09abc require NSS 3.32, r=me
Priority: -- → P1
a few thousand new compiler warnings with this: == Change summary for alert #7246 (as of June 13 2017 13:59 UTC) == Regressions: 36% compiler warnings summary osx-10-7-noopt debug 4,823.17 -> 6,546.50 For up to date results, see: https://treeherder.mozilla.org/perf.html#/alerts?id=7246 I don't know if we have a policy for this, but ask around in #build if there is a policy, this is more for information.
> 36% compiler warnings summary osx-10-7-noopt debug 4,823.17 -> 6,546.50 The only new warnings I can see (without having something like a diff) are confused expansions of intrinsics. I'm not sure if we can do anything about that.
Pushed by email@example.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/dc534de59f01 land NSS 825e5d444e99 UPGRADE_NSS_RELEASE, r=me
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/mozilla-inbound/rev/be884de5820a land NSS f212be04f3d0 UPGRADE_NSS_RELEASE, r=me
Pushed by email@example.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/5b4c249619e5 uplift NSS_3_32_RTM, no code changes, only version numbers, r=me
You need to log in before you can comment on or make changes to this bug.