Closed Bug 578005 Opened 15 years ago Closed 15 years ago

Investigate why *_l10n_verification step failed for 3.0.6 build 2

Categories

(Mozilla Messaging Graveyard :: Release Engineering, defect)

Product:
Mozilla Messaging Graveyard
Component:
Release Engineering
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(blocking-thunderbird3.0 .6+, thunderbird3.0 .6-fixed)

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
blocking-thunderbird3.0 --- .6+
thunderbird3.0 --- .6-fixed

People

(Reporter: standard8, Assigned: gozer)

References

Details

(Whiteboard: [non-code])

L10n verification failed on all three platforms for 3.0.6 build 2. The specific steps that failed were: - verify_l10n, verify_l10n_2 Both with "./verify_l10n.sh: line 19: [: too many arguments" and - l10n_metadiff diff: thunderbird-3.0.6-build2/diffs: No such file or directory diff: thunderbird-3.0.5-build2/diffs: No such file or directory (presumably a result of the previous two steps failing). Marking this as a non-code blocker for 3.0.6 as we could have hidden l10n issues if we don't know if this has actually worked or not.
This was introduced by an upstream change to buildbotcustom that splits the verification steps per platform. Working on a fix.
Status: NEW → ASSIGNED
Updated to latest buildbotcustom/ fixed it on linux/mac. Windows now requires rsync.exe, and not yet sure where it's supposed to be coming from.
Ah, my bad, even thought the verification step was broken out per platform, the verification itself still needs running on a mac.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.