Closed Bug 651923 Opened 14 years ago Closed 14 years ago

Re-run update verify on 3.6.17 (beta/betatest channel)

Categories

(Release Engineering :: General, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: christian, Assigned: coop)

Details

Please re-run update verify on 3.6.17 (beta/betatest channel). We are seeing very low ADUs and would like to verify everything is in the correct place as far as snippets are concerned. I notice there is a lot of churn in https://wiki.mozilla.org/Releases/Firefox_3.6.17/BuildNotes#Updates so I would like it double checked. Thanks!
Priority: -- → P1
Assignee: nobody → coop
Status: NEW → ASSIGNED
Update verify is being run against the betatest channel which points to build3 at the moment. I ran update verify for build3 tonight and it went quite good: https://wiki.mozilla.org/Releases/Firefox_3.6.17/BuildNotes#Update_Verify_2 I think, it's possible to run update verify against the beta channel build2 by running the code manually with some local changes.
Status: ASSIGNED → NEW
Or, if there is another way to test the correct snippets are in the proper place that would be great as well (I know nthomas had some sort of matrix tool somewhere).
(In reply to comment #0) > Please re-run update verify on 3.6.17 (beta/betatest channel). These have been kicked off.
Update verify has already returned for Windows showing no errors. Other platforms will take a few more hours to complete.
One transient error on Linux: FAIL: no complete update found for https://aus2.mozilla.org/update/1/Firefox/3.6.8/20100722145641/Linux_x86-gcc3/fi/betatest/update.xml?force=1 FAIL: download_mars returned non-zero exit code: 1 I checked the file by hand and it's there. No errors on Mac.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Ok, thanks for checking that!
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.