Bug 96492
| Summary: | [Chromium] A lot of tests on Android have stderr output due to getMimeTypeFromExtension | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Peter Beverloo <peter> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | pliard |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 96398, 100100 | ||
Peter Beverloo
Example output:
http://build.webkit.org/results/Chromium%20Android%20Release%20(Tests)/r128190%20(72)/dom/html/level2/html/HTMLCollection11-stderr.txt
This definitely needs to be fixed on the Chromium side, but filing here for clarity as it's causing a lot of failures. We should find out why this call is failing. Philippe's patch on Bug 95690 may be related.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Peter Beverloo
After amending the error to be clearer, one extension that is at fault seems to be .js.
[WARNING:network_library.cc(83)] Call to getMimeTypeFromExtension failed for extension js
Peter Beverloo
I uploaded a Chromium-side patch which addresses this:
https://codereview.chromium.org/11293101/
It turns out that we're throwing the warning on the most popular extensions (js) for no reason, as they'll be resolved slightly later on. Having no available mime-type for others (i.e. ttf) will degrade gracefully, and the font will be loaded anyway.
Marking this as fixed as no action is required on the WebKit side of things.