Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upMake font template data load fallible #12076
Conversation
highfive
commented
Jul 1, 2016
|
Reviewed 4 of 4 files at r1. components/gfx/font_template.rs, line 157 [r1] (raw file):
Remove extra parenthesis. components/gfx/platform/freetype/font_template.rs, line 6 [r1] (raw file):
Any reason why Comments from Reviewable |
|
Review status: all files reviewed at latest revision, 2 unresolved discussions. components/gfx/platform/freetype/font_template.rs, line 6 [r1] (raw file):
|
|
@pcwalton Any idea what would be required in order to test this? |
|
No idea about test stuff, but this is gathering dust. Let's review! |
|
I don't know how testable this is. I think the error path only happens when the OS reports a font as installed but we couldn't open it for whatever reason, right? |
|
Sounds plausible. |
|
The only way I could think of to test this would be to either artificially simulate I/O errors or to do something silly like have the test harness set permissions on fonts to make them temporarily unreadable. |
|
@bors-servo: r=pcwalton |
|
|
|
|
Make font template data load fallible Remove a TODO around dealing with a failed file operation. Can we write an automated test for this? I don't really know what font template data is, but this failure seems to be fontconfig-specific... --- - [X] `./mach build -d` does not report any errors - [X] `./mach test-tidy` does not report any errors - [X] These changes fix #12037 - [ ] There are tests for these changes OR - [ ] These changes do not require tests because _____ <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="35" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/12076) <!-- Reviewable:end -->
|
|
|
@bors-servo: retry |
Make font template data load fallible Remove a TODO around dealing with a failed file operation. Can we write an automated test for this? I don't really know what font template data is, but this failure seems to be fontconfig-specific... --- - [X] `./mach build -d` does not report any errors - [X] `./mach test-tidy` does not report any errors - [X] These changes fix #12037 - [ ] There are tests for these changes OR - [ ] These changes do not require tests because _____ <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="35" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/12076) <!-- Reviewable:end -->
|
|
jdm commentedJul 1, 2016
•
edited by larsbergstrom
Remove a TODO around dealing with a failed file operation.
Can we write an automated test for this? I don't really know what font template data is, but this failure seems to be fontconfig-specific...
./mach build -ddoes not report any errors./mach test-tidydoes not report any errorsThis change is