Closed Bug 1421535 Opened 7 years ago Closed 7 years ago

57.0.x special handling for updates

Categories

(Release Engineering :: Release Requests, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jlund, Unassigned)

References

Details

Attachments

(1 file)

context, example UV task that failed: bys2tlHvQj-VKrL9ICpXAQ earlier: run0 example log: FAIL: expected buildID 20171128222554 does not match actual 20171112125346 FAIL: [48.0.2 de complete] download_mars returned non-zero exit code: 1 irc: jlund> Jordan Lund k, UV is running. Just partner tasks left so I will create the wnp blob now 21:19:48 done. 4 rules updated too 21:21:21 release-cdntest updated too 21:23:33 — •jlund reruns failed osx UV task bys2tlHvQj-VKrL9ICpXAQ to test that fixes later: run1 example log: FAIL: [33.0.3 ru complete] check_updates returned failure for Darwin_x86_64-gcc3-u-i386-x86_64 downloads/Firefox 33.0.3.dmg vs. downloads/Firefox 57.0.1.dmg: 1 irc: 22:15:08 <•jlund> Jordan Lund dang. still failed 22:16:20 <•jlund> Jordan Lund looks more serious. 22:16:57 perhaps my wnp blobs generated by create_wnp_blob.py are no good
similar to: https://bugzilla.mozilla.org/show_bug.cgi?id=1413645#c4 I first ran the following: python create_wnp_blob.py --blob Firefox-57.0.1-build1-bz2 fx 57.0.1build1 'https://www.mozilla.org/%LOCALE%/firefox/57.0.1/whatsnew/?oldversion=%OLD_VERSION%' > ~/Firefox-57.0.1-build1-bz2-WNP.json python create_wnp_blob.py --blob Firefox-57.0.1-build1 fx 57.0.1build1 'https://www.mozilla.org/%LOCALE%/firefox/57.0.1/whatsnew/?oldversion=%OLD_VERSION%' > ~/Firefox-57.0.1-build1-WNP.json I then took those blobs and uploaded them. Finally, I updated the following release-localtest rules (and release-cdntest equivalents): - 674 - 668 - 675 - 667
Why do we need that ? Some of the rules for Linux and Mac need data from %OS_VERSION% to make sure the rules are considered, which is only sent in update/6/.
See Also: → 1415557
https://hg.mozilla.org/build/tools/rev/768ee6fec8cf6cbe836ec48d08e10c4245d8ab72 Bug 1421535 - set OS_VERSION and SYSTEM_CAPABILITIES in update verify; update release configs to remove watersheds, based on rev 1afe9b0b3f4d https://hg.mozilla.org/build/tools/rev/cbbcb57e6539d0291805a42bb59d5a8c68ff060a backout bug 1421535 - rev 768ee6fec8cf
bc of build2, these steps were needed again: [create-wnp]jlund@dale-493:~/devel/mozilla/releaseduty λ python create_wnp_blob.py --blob Firefox-57.0.1-build2-bz2 fx 57.0.1build2 'https://www.mozilla.org/%LOCALE%/firefox/57.0.1/whatsnew/?oldversion=%OLD_VERSION%' > ~/Firefox-57.0.1-build2-bz2-WNP.json [create-wnp]jlund@dale-493:~/devel/mozilla/releaseduty λ python create_wnp_blob.py --blob Firefox-57.0.1-build2 fx 57.0.1build2 'https://www.mozilla.org/%LOCALE%/firefox/57.0.1/whatsnew/?oldversion=%OLD_VERSION%' > ~/Firefox-57.0.1-build2-WNP.json rule updates: - 674 - 668 - 675 - 667 https://hg.mozilla.org/build/tools/pushloghtml?fromchange=13007f97430c&tochange=112dfd3249b9 rerunning failed UV to verify now.
Summary: 57.0.1 Update Verify is failing → 57.0.x special handling for updates
For 57.0.2 build2 * we're only updating Windows to 57.0.2; Mac and Linux will stay on 57.0.1 * jlund has done the equivalent of comment #5 for Firefox-57.0.2-build2-WNP.json. We don't need a bz2-WNP because only mac and linux use that * tools hackery in https://hg.mozilla.org/build/tools/pushloghtml?fromchange=f473439aca79&tochange=482b82c788c1 * backs out u.v. changes for mac and linux * adds the changes to verify.sh to support JAWS and memory parameters * trims u.v. configs for all platforms as we've been doing * config changes for bhearsum's checker script * https://hg.mozilla.org/users/bhearsum_mozilla.com/tools/rev/e144c3c6223aeecc11d63dfae710c674601d9bf1 * https://hg.mozilla.org/users/bhearsum_mozilla.com/tools/rev/408cc99ee905483179094de7932a19ea04172064 * assorted rule changes tracked in https://docs.google.com/document/d/1YAkQU7Is7FLdxKtiNBPH_e6-5Nik4rQpCLNGJHIuSjo/edit# With that we're green on Ben's script for release-localtest and release-cdntest. Update verify jobs are rerunning against release-localtest.
https://hg.mozilla.org/build/tools/rev/352777d48a3923edffc773451253f3d4fe1292fc Bug 1421535 - set OS_VERSION and SYSTEM_CAPABILITIES in update verify; update release configs to remove watersheds, based on rev 1afe9b0b3f4d https://hg.mozilla.org/build/tools/rev/2521ba1c3c653a3c4d4062f6f24b373ff10bb763 backed out Bug 1421535 - rev: 352777d48a39
for 57.0.3 - done: * removed 57.0.1 freeze for linux/darwin * generated wnp for 57.0.3 (+ bz2 equivalent) * relanded and retagged patcher patches: https://hg.mozilla.org/build/tools/pushloghtml?fromchange=6d6c484ff822&tochange=2521ba1c3c65 currently: * rerunning failed update verify tasks.
release-localtest / release-cdntest ready. Ben's script says "Everything is Awesome". patch was larger than expected as we no longer support partials in any WNP based blob: https://hg.mozilla.org/users/bhearsum_mozilla.com/tools/rev/9205614b0e9b65ea6a97a2a76c91e1b9e553192d # replace with your local paths $ python3 update-status.py gather_results -a https://aus5.mozilla.org -j32 --version 56.0 --version 56.0.1 --version 56.0.2 --version 55.0 --version 55.0.1 --version 55.0.2 --version 55.0.3 --version 57.0 --version 57.0.1 --version 57.0.2 $REP/tools/release/patcher-configs/mozRelease-branch-patcher2.cfg release-cdntest /tmp/release-57.0.3.json $ python update-status.py write_report --verify-data update-status-57.0.3.yml /tmp/release-57.0.3.json /tmp/release.html release channel is scheduled but needs 1st: go from relman, 2nd: update datetime of impl, 3rd: sign off
Bulk change of QA Contact to :jlund, per https://bugzilla.mozilla.org/show_bug.cgi?id=1428483
QA Contact: catlee → jlund
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: