400103 - fix patcher/updateVerify config mismatches

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Robert Helmer [:rhelmer]]

Attachment: fix patcher/updateVerify config mismatches

Since we started doing test aus2 runs (bug 389206), a few differences in the patcher config and the updateVerify config have come to light. Staging is currently working end-to-end with the following failures (no updates available for "ka" 2.0.0.2/2.0.0.3, and "ja-JP-mac" not specified as valid 2.0b1 locale).

We should remove "ka" from the verify config, and add "ja-JP-mac" to the patcher config.

FAIL: no partial update found for staging-build-console.build.mozilla.org/update/1/Firefox/2.0.0.3/2007030919/Darwin_Universal-gcc3/ka/betatest/update.xml
 FAIL: download_mars returned non-zero exit code: 1
 FAIL: no complete update found for staging-build-console.build.mozilla.org/update/1/Firefox/2.0.0.3/2007030919/Darwin_Universal-gcc3/ka/betatest/update.xml
 FAIL: download_mars returned non-zero exit code: 1
 FAIL: no partial update found for staging-build-console.build.mozilla.org/update/1/Firefox/2.0.0.2/2007021917/Darwin_Universal-gcc3/ka/betatest/update.xml
 FAIL: download_mars returned non-zero exit code: 1
 FAIL: no complete update found for staging-build-console.build.mozilla.org/update/1/Firefox/2.0.0.2/2007021917/Darwin_Universal-gcc3/ka/betatest/update.xml
 FAIL: download_mars returned non-zero exit code: 1
 FAIL: no partial update found for staging-build-console.build.mozilla.org/update/1/Firefox/2.0b1/2006071020/Darwin_Universal-gcc3/ja-JP-mac/betatest/update.xml
 FAIL: download_mars returned non-zero exit code: 1
 FAIL: no complete update found for staging-build-console.build.mozilla.org/update/1/Firefox/2.0b1/2006071020/Darwin_Universal-gcc3/ja-JP-mac/betatest/update.xml
 FAIL: download_mars returned non-zero exit code: 1

Comment 1

[Nick Thomas [:nthomas] (UTC+12)]

Comment on attachment 285188 [details] [diff] [review]
fix patcher/updateVerify config mismatches

Turns out I didn't fully understand the situation when we talked a day ago. Those errors are empty update.xml rather than missing mar files. So for the ka case, if you compare these

http://staging-build-console.build.mozilla.org/update/1/Firefox/2.0.0.3/2007030919/Darwin_Universal-gcc3/ka/betatest/
http://aus2.build.mozilla.org/update/1/Firefox/2.0.0.3/2007030919/Darwin_Universal-gcc3/ka/betatest/

then the staging version is empty and prod correctly points to 2.0.0.4. Looking at the snippets on disk, aus2 has
  /opt/aus2/incoming/3/Firefox/2.0.0.3/Darwin_Universal-gcc3/2007030919/ka/
with betatest/, release/, releasetest/ dating from May 23 (which corresponds to the prep time for 2.0.0.4). There's nothing equivalent on staging-build-console, so it seems patcher doesn't create snippets correctly in the past release case (only <current update>). Might be related to bug 384065.

I'd prefer we still check that mac ka 2.0.0.1 thru 2.0.0.3 have updates to 2.0.0.4. (By the way, 2.0.0.1 is on the ftp and in shipped-locales but not in the verify). So probably the best plan of attack is to take a backup of aus2.m.o snippets from before 2.0.0.7 and unpack it on staging-build-console. Sound ok ?

The ja-JP-mac part looks fine. There are betatest snippets on aus2.m.o from Aug 31 2006, pointing to 2.0b2, so that's why the production automation doesn't fail.

Comment 2

[Robert Helmer [:rhelmer]]

Attachment: [checked in]just fix ja-JP-mac in patcher.cfg

Alright, this just fixes patcher.cfg and leaves the update verify config alone.
To fix the .2/.3 "ka" osx problem, I'm going to copy over the following AUS dirs to staging-build-console:

/opt/aus2/incoming/3/Firefox/2.0.0.2/Darwin_Universal-gcc3/2007021917/ka/
/opt/aus2/incoming/3/Firefox/2.0.0.3/Darwin_Universal-gcc3/2007030919/ka/

Comment 3

[Robert Helmer [:rhelmer]]

These URLs now work:
http://staging-build-console.build.mozilla.org/update/1/Firefox/2.0.0.3/2007030919/Darwin_Universal-gcc3/ka/betatest/
http://staging-build-console.build.mozilla.org/update/1/Firefox/2.0.0.2/2007021917/Darwin_Universal-gcc3/ka/betatest/

Comment 4

[Nick Thomas [:nthomas] (UTC+12)]

Comment on attachment 285281 [details] [diff] [review]
[checked in]just fix ja-JP-mac in patcher.cfg

Thanks Rob.

Comment 5

[Robert Helmer [:rhelmer]]

Comment on attachment 285281 [details] [diff] [review]
[checked in]just fix ja-JP-mac in patcher.cfg

Checking in moz18-branch-patcher2.cfg;
/mofo/release/patcher/moz18-branch-patcher2.cfg,v  <--  moz18-branch-patcher2.cfg
new revision: 1.45; previous revision: 1.44
done

Comment 6

[Robert Helmer [:rhelmer]]

Loaded the new moz18-branch-patcher2.cfg into the cvsmirrors on staging-build-console as well. Thanks Nick!