cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Grieve <>
Subject Re: mobile spec pass rate sizable drop on android
Date Mon, 21 Jan 2013 18:27:08 GMT
Fil, is there any way on to see which tests are failing and
on which devices?

AFAIK, the slice() tests that braden added *should* be passing on both iOS
& Android. If they are not, we should fix them.

I added one test that checks that native Blob objects still work with
FileReader. The test fails on iOS 5 since iOS5 does not support the Blob
constructor, and they also fail on Android < 3.0 since it doesn't support
the File API natively. We could just do a version check on Android < 3 &
iOS < 6 to make skip the test.

The relevant bug for it is here:
There are sub-bugs for BB and WP. Not sure if anyone has the intention of
addressing this for this release? For the JS-based platforms, the
implementation should be quite easy, in that you can just use the
platform's Blob.slice method.

On Mon, Jan 21, 2013 at 1:07 PM, Filip Maj <> wrote:

> Hey everyone,
> Working over the weekend on the ci dashboard I noticed that the pass rate
> on android for mobile-spec dropped from ~95% to ~85%. It looks like the
> majority of failures are due to new tests for the File slice stuff that
> was added recently, perhaps also related to the Blob stuff.
> If you head to and click on the outer pie chart pieces
> (representing individual devices) you'll see a list of failures on
> particular devices.
> It looks like some of this stuff is failing on iOS too (there's a Blob
> constructor failure), but there is only one failure on iOS vs. 35+ on
> Android.
> Additionally, this is just on two platforms. Not sure what the situation
> is on BlackBerry, WP, and our other supported platforms, but I'm assuming
> no work was done on the new APIs for these platforms.
> Andrew/Michal/Braden you guys were working on this stuff, ya? Are we going
> to ship incomplete slice and blob implementations for 2.4.0rc1? I don't
> care if we do, but I do care about cross-platform parity for new features
> being shipped, and I'm concerned there is no plan for that with this new
> File API addition.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message