Closed
Bug 1307016
Opened 8 years ago
Closed 8 years ago
Tests should output ascii for compatibility with terminals
Categories
(Testing Graveyard :: external-media-tests, defect)
Testing Graveyard
external-media-tests
Tracking
(firefox52 fixed)
RESOLVED
FIXED
mozilla52
Tracking | Status | |
---|---|---|
firefox52 | --- | fixed |
People
(Reporter: bryce, Assigned: bryce)
References
Details
Attachments
(1 file)
During refactoring of the tests I've changed the logging and removed some of the forced conversions to ascii. However, it appears that the jenkins test machines do not all play nice with this. Thus, for now I think it appropriate that the tests again convert all output that may contain non-ascii characters to ascii. I think there is merit in a more robust approach where we use the widest character set available to us. However, I'd think it better to address that in a follow up. My thinking for this is we currently have the tests running on at least 3 separate platforms (custom Jenkins nodes, Build bot, Task cluster), and I'd rather wait until we've reached a more standardised setting before making those changes.
Comment hidden (mozreview-request) |
Comment 2•8 years ago
|
||
mozreview-review |
Comment on attachment 8797816 [details] Bug 1307016 - Have puppeteer __str__ encode fields to ascii. https://reviewboard.mozilla.org/r/83426/#review82324 Note: there's a typo in the commit message -- ascii.
Attachment #8797816 -
Flags: review?(mjzffr) → review+
Comment hidden (mozreview-request) |
Pushed by bvandyk@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/c0817cce76da Have puppeteer __str__ encode fields to ascii. r=maja_zf
Comment 5•8 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/c0817cce76da
Status: NEW → RESOLVED
Closed: 8 years ago
status-firefox52:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla52
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → bvandyk
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 6•8 years ago
|
||
Bryce, do we need to backout the patch as landed or why did you reopen the bug? If follow-up work is needed it should be done on a follow-up bug. This one should be kept as fixed.
Flags: needinfo?(bvandyk)
Assignee | ||
Comment 7•8 years ago
|
||
Ah, okay, my bad. The work can be done in a follow up then. I was unfamiliar with the convention.
Status: REOPENED → RESOLVED
Closed: 8 years ago → 8 years ago
Flags: needinfo?(bvandyk)
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•