Closed Bug 552668 Opened 15 years ago Closed 15 years ago

l10n verify should be unpacking jar files

Categories

(Release Engineering :: General, defect, P2)

All
macOS
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bhearsum, Assigned: rail)

References

Details

(Whiteboard: [automation])

Attachments

(3 files, 1 obsolete file)

During the 3.5.9 release I noticed that l10n verify doesn't diff anything contained in jar files. Since so many strings are packed into jar files we should be unpacking them before running l10n verify. We miss a lot of string changes by ignoring these, which could potentially make us miss issues.
Attached patch Unpack JAR files (obsolete) — Splinter Review
Something like this?
Attachment #458301 - Flags: feedback?(bhearsum)
Comment on attachment 458301 [details] [diff] [review] Unpack JAR files This seems like it would work. It'd be great to have l10n verify re-run for something like 3.6b1 - 3.6b2, or something else guaranteed to have string changes as a test for this.
Attachment #458301 - Flags: feedback?(bhearsum) → feedback+
during testing the patch in staging I found that verify_l10n.sh calls unpack_build() and passes wildcard here: http://hg.mozilla.org/build/tools/file/6c1a3110a600/release/l10n/verify_l10n.sh#l28 As a result for locale (luckily txt comes after the installers) becomes firefox-3.6.8-build1/linux-i686/en-US/firefox-3.6.8.txt instead of "en-US". To prevent this we shouldn't rsync *.txt files.
Assignee: nobody → rail
Status: NEW → ASSIGNED
Attachment #462064 - Flags: review?(bhearsum)
Attached patch Unpack JAR filesSplinter Review
* Use -o (override) parameter to prevent console interaction * Redirect stdout to /dev/null as in other unzip commands in the same file * Add -N parameter to diff, so it creates diffs for new files. Otherwise it doesn't produce diffs for localized content (en-US.jar.dir vs ab_CD.jar.dir).
Attachment #458301 - Attachment is obsolete: true
Attachment #462071 - Flags: review?(bhearsum)
Attachment #462064 - Flags: review?(bhearsum) → review+
Comment on attachment 462071 [details] [diff] [review] Unpack JAR files Seems reasonable. I'd be interested in seeing the output from a staging run, though.
Attachment #462071 - Flags: review?(bhearsum) → review+
(In reply to comment #5) > I'd be interested in seeing the output from a staging run, though. Sure, on moz2-darwin9-slave03: /builds/slave/*_l10n_verification/tools/release/l10n/firefox*/diffs/* Buildbot output is almost the same, on sm: /builds/buildbot/moz2-master/*_l10n_verification/
Priority: P5 → P2
(In reply to comment #6) > (In reply to comment #5) > > I'd be interested in seeing the output from a staging run, though. > > Sure, on moz2-darwin9-slave03: > /builds/slave/*_l10n_verification/tools/release/l10n/firefox*/diffs/* > > Buildbot output is almost the same, on sm: > /builds/buildbot/moz2-master/*_l10n_verification/ Looks good. Land at your convenience!
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
The patch affects update verify factory which uses the same function. JAR files should be unpacked only for l10n verification.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Attachment #467776 - Flags: review?(bhearsum)
Attachment #467776 - Flags: review?(bhearsum) → review+
Attachment #467776 - Flags: checked-in+
Status: REOPENED → RESOLVED
Closed: 15 years ago15 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: