Closed
Bug 577310
Opened 14 years ago
Closed 14 years ago
prefer ascii over unicode for build logs
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rhelmer, Assigned: timeless)
References
Details
Attachments
(1 file, 2 obsolete files)
8.53 KB,
patch
|
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
As noticed in bug 474657 and bug 446505, gcc is putting unicode characters into build logs. Bug 474657 makes tinderbox set the content-type to UTF-8 for all logs, which is much heavier than ASCII (especially due to bug 566066). I don't think there's any reason for gcc to emit unicode, it should be told to use ASCII only by setting the locale to C by setting LC_ALL=C in the environment per bug 390341 comment 38. Please note that this isn't necessarily specific to bug 390341, this is going to be a problem no matter how the build logs are served, if they are intended to be viewed in the browser.
is this right? i don't have any way of testing this :(
Attachment #457699 -
Flags: review?
Comment 2•14 years ago
|
||
that looks like it would only take effect for mobile builds and not properly because of how we invoke scratchbox.
@@ -309,6 +315,7 @@ PLATFORM_VARS = { and following should be for non scratchbox stuff. hrm, i'll have to find a scratchbox log and see if it's affected by this, if not, then i can drop those bits....
Comment 4•14 years ago
|
||
The PLATFORM_VAR parts seem fine to me. If you drop the MOBILE_PLATFORM_VARS stuff for now we could land this for the other platforms while that gets figured out.
bhearsum said he'd land this since it requires coordinating with buildbot
Assignee: nobody → timeless
Attachment #457699 -
Attachment is obsolete: true
Status: NEW → ASSIGNED
Attachment #457818 -
Flags: review?(bhearsum)
Attachment #457699 -
Flags: review?
Comment 6•14 years ago
|
||
Comment on attachment 457818 [details] [diff] [review] patch for PLATFORM_VARS I'll try to get this landed today.
Attachment #457818 -
Flags: review?(bhearsum) → review+
Comment 7•14 years ago
|
||
specifically, i don't think we pass the build time environment to scratchbox during the build step. We can land it for all non-scratchbox builds (android and desktop builds).
Comment 8•14 years ago
|
||
I'll land this in the downtime tomorrow.
Comment 9•14 years ago
|
||
I'll be landing this tomorrow morning.
Updated•14 years ago
|
Attachment #457818 -
Attachment is obsolete: true
Comment 10•14 years ago
|
||
Comment on attachment 459110 [details] [diff] [review] add LC_ALL for non-scratchbox OS' which use gcc changeset: 2737:8d80f9421169
Attachment #459110 -
Flags: checked-in+
Comment 11•14 years ago
|
||
Anything else we need to do here?
Filed bug 581164 on the remaining force-ascii issue.
Comment 13•14 years ago
|
||
i'm pretty sure we've got LC_ALL in all the right places, so it sounds like we're done here.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•