96492 2012-09-12 04:09:31 -0700 [Chromium] A lot of tests on Android have stderr output due to getMimeTypeFromExtension 2012-11-05 12:15:17 -0800 1 1 1 Unclassified WebKit Tools / Tests 528+ (Nightly build) Unspecified Unspecified RESOLVED FIXED P2 Normal --- 96398 100100 1 peter webkit-unassigned pliard oldest_to_newest 718167 0 peter 2012-09-12 04:09:31 -0700 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. 718265 1 peter 2012-09-12 05:48:25 -0700 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 758775 2 peter 2012-11-05 12:15:17 -0800 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.