Update balrog rules to serve ARM Widevine 4.10.2557.0 to Windows ARM users
Categories
(Release Engineering :: General, task)
Tracking
(Not tracked)
People
(Reporter: aosmond, Assigned: gbrown)
References
Details
Attachments
(1 file)
5.07 KB,
text/x-python
|
Details |
In bug 1801201, we updated the balrog rules for Widevine 4.10.2557.0 on all channels.
Given the work in bug 1811981, we will soon support loading both ARM and x86 Widevine on Windows ARM, instead of just x86 Widevine. This appears to resolve crashes related to starting the plugin, and allows the playback of DRM content.
Initially we would just like to create a channel for QA to use for verification.
Reporter | ||
Updated•2 years ago
|
Reporter | ||
Comment 1•2 years ago
|
||
This script will generate the JSON required to use the ARM Widevine plugin on Windows ARM:
{
"hashFunction": "sha512",
"name": "Widevine-4.10.2557.0",
"schema_version": 1000,
"vendors": {
"gmp-widevinecdm": {
"platforms": {
"Darwin_aarch64-gcc3": {
"fileUrl": "https://redirector.gvt1.com/edgedl/widevine-cdm/4.10.2557.0-mac-arm64.zip",
"filesize": 8087979,
"hashValue": "23d7fbf6c80ff0341bf454169e1174ccaf9ded617eab648d48edcbc0bce9ddf4fc917c6ad7dd3119d27fc634958df39bd8f2f642f729a1c092efe27974cc6897"
},
"Darwin_x86_64-gcc3": {
"alias": "Darwin_x86_64-gcc3-u-i386-x86_64"
},
"Darwin_x86_64-gcc3-u-i386-x86_64": {
"fileUrl": "https://redirector.gvt1.com/edgedl/widevine-cdm/4.10.2557.0-mac-x64.zip",
"filesize": 9160906,
"hashValue": "f0bdaedb4d89ab96de523212092281b6b297c8e15904ca264b4b0422916d5504deab0f6baacc8324fef3493dd9ff08cb98e0ccdbc08c3b16c79576f8126c3471"
},
"Linux_x86_64-gcc3": {
"fileUrl": "https://redirector.gvt1.com/edgedl/widevine-cdm/4.10.2557.0-linux-x64.zip",
"filesize": 7806686,
"hashValue": "55a7e4b379d5826f01b1a36abd872f411b0ba3cd2edec0c799e82def02f171df1e33365f58d91d2527f1dcaf3644b0ba9f5c4a31e712bee42bc786a545a3491c"
},
"Linux_x86_64-gcc3-asan": {
"alias": "Linux_x86_64-gcc3"
},
"WINNT_aarch64-msvc-aarch64": {
"fileUrl": "https://redirector.gvt1.com/edgedl/widevine-cdm/4.10.2557.0-win-arm64.zip",
"filesize": 7780530,
"hashValue": "5fba54f885efd82976011bd6de2ac191fced96a7184b829e975418c36b2bcdaa78af0733f4e41200933f5e81ddac996b9632b62c10e1e42bcb0bff8faa7ffa55"
},
"WINNT_x86-msvc": {
"fileUrl": "https://redirector.gvt1.com/edgedl/widevine-cdm/4.10.2557.0-win-x86.zip",
"filesize": 8082561,
"hashValue": "7dc3698651a81361e15ec6ce4776e4b7dc92dea360265ca0fa819d7dccee7e0545c1dffae7ba2ebece502ec90c491da0ed2b5ebd1108122e1d30df23d456eb3e"
},
"WINNT_x86-msvc-x64": {
"alias": "WINNT_x86-msvc"
},
"WINNT_x86-msvc-x86": {
"alias": "WINNT_x86-msvc"
},
"WINNT_x86_64-msvc": {
"fileUrl": "https://redirector.gvt1.com/edgedl/widevine-cdm/4.10.2557.0-win-x64.zip",
"filesize": 8435708,
"hashValue": "b046dd1b26ec0b810ee441b7ad4dc135e3f1521a817b9f3db60a32976352e8f7e53920e1a77fc5b4130aac260d79deef7e823267b4414e9cc774d8bffca56a72"
},
"WINNT_x86_64-msvc-x64": {
"alias": "WINNT_x86_64-msvc"
},
"WINNT_x86_64-msvc-x64-asan": {
"alias": "WINNT_x86_64-msvc"
}
},
"version": "4.10.2557.0"
}
}
}
Reporter | ||
Comment 2•2 years ago
|
||
To be clear, this is not to be shipped to any of our official release channels at this time (nightly/beta/release/esr), only to be considered for nightlytest
once bug 1811981 lands.
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 3•2 years ago
|
||
Assignee | ||
Comment 4•2 years ago
|
||
I created a new Widevine release in Balrog, with the script output unaltered; it only differs from the existing release in the WINNT_aarch64-msvc-aarch64 section.
I created a new rule for the nightlytest channel pointing to the new release: aarch64 is now available on the nightlytest channel only.
Reporter | ||
Comment 5•2 years ago
|
||
From QA's smoke testing, the Widevine ARM plugin appears to be stable and working well. Could we now roll the rule out to the nightly
channel for further testing/verification? Thanks!
(Note that we are landing bug 1819661 in parallel. It does not block the channel update, although is related.)
Assignee | ||
Comment 6•2 years ago
|
||
Now rolled out to nightly
channel as well.
Reporter | ||
Comment 7•2 years ago
|
||
I realized I made a mistake in my previous requests, by not specifying a minimum Firefox version for our updated rules. This bug depends on bug 1811981, which only landed in Firefox 111 nightly. It is unlikely many, if any users, were impacted, but it does have the potential to break mozregression on Windows ARM, if one were testing the EME plugins.
Could we please update the nightly
channel to require 111 as the minimum version? Older versions should use the same rule as before, pointing to the x86 version instead.
Additionally, QA has verified this on the nightly
channel. Could we please we can roll this out to the beta
channel, again with 111 as the minimum version?
Thanks!
Assignee | ||
Comment 8•2 years ago
|
||
I have updated the nightly
channel to require 111 as the minimum version for the arm64 plugin.
I have a similar change queued up for beta
but that's waiting on a signoff (independent approval) and might not happen today.
Assignee | ||
Comment 9•2 years ago
|
||
Windows arm64 is now active on beta
also, for version >= 111.0.
Comment 10•2 years ago
|
||
retitling since this isn't about nightlytest anymore.
Reporter | ||
Comment 11•2 years ago
|
||
QA has verified this on the beta
channel and given us the all clear there. I believe we are good to roll this out to release and finally put this issue to bed :).
Could we please roll this out to the release
channel, once again with 111 as the minimum version?
I'd like to re-iterate that because Firefox 111 doesn't have bug 1814910, users for 111 will require manual intervention to get the update after it is applied to balrog. This can be achieved a number of ways:
- With a fresh profile
- Manually deleting the
gmp-widevinecdm
folder in an existing profile and restarting Firefox - Toggling the
Play DRM-controlled content
setting inabout:preferences
should delete the plugin directories
I've requested uplift of the related patches to both 111 and 102 ESR.
Assignee | ||
Comment 12•2 years ago
|
||
:bhearsum and/or :jcristau - I have rule changes queued up in Balrog; can you double-check for me? Is it better to use <111 or <111.0a1 here?
https://balrog.services.mozilla.com/rules?product=Widevine#scId=4870
(Once those are live, I plan to delete 425, 426, 427).
Comment 13•2 years ago
|
||
(In reply to Geoff Brown [:gbrown] from comment #12)
:bhearsum and/or :jcristau - I have rule changes queued up in Balrog; can you double-check for me? Is it better to use <111 or <111.0a1 here?
https://balrog.services.mozilla.com/rules?product=Widevine#scId=4870
Looks fine to me. 111.0a1 vs 111.0 doesn't really matter since nightly's been getting the new blob for weeks and has moved on to 113 by now.
(Once those are live, I plan to delete 425, 426, 427).
Sounds good (for the record 425/426/427 are the priorities for the current nightlytest/nightly/beta rules; their ids are 17801/17802/17804).
Assignee | ||
Comment 15•2 years ago
|
||
Live now: aarch64 available for version 111 and above on all channels.
Assignee | ||
Comment 16•2 years ago
•
|
||
(In reply to Geoff Brown [:gbrown] from comment #15)
Live now: aarch64 available for version 111 and above on all channels.
...except ESR!
aosmond: Since this is for >=111, I suppose we don't want this for esr-102 yet, but will want it for future esr, and probably for esr-102 at some time?
Reporter | ||
Comment 17•2 years ago
|
||
We just uplifted the necessary patches to 102 ESR. I will let you know once QA has verified it.
Assignee | ||
Updated•2 years ago
|
Reporter | ||
Comment 18•2 years ago
|
||
QA has verified 102.10.0 ESR is working from a treeherder build. I don't expect official builds to be produced for another 2 weeks, but at this point, it should be safe to roll this out to the esr102
channel for versions greater than or equal to 102.10.0
.
Assignee | ||
Comment 19•2 years ago
|
||
Available now on esr for >=102.10.0.
Reporter | ||
Comment 20•2 years ago
|
||
Thank you, gbrown!
Description
•