cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shazron <shaz...@gmail.com>
Subject Re: mobile spec pass rate sizable drop on android
Date Mon, 21 Jan 2013 22:58:12 GMT
I tested with the cordova-js 2.4.0rc1, and all tests pass. There is one
intermittent failure though, relating to Media.position, which doesn't seem
a blocker to me (see attached screenshot). Might be related to:
https://issues.apache.org/jira/browse/CB-1452

[image: Inline image 1]


On Mon, Jan 21, 2013 at 1:04 PM, Shazron <shazron@gmail.com> wrote:

> I updated the cordova-js on iOS with cordova-js commit
> 1aa3643deaa9f14970806277d5f651f3cd78caa9 (the latest as of this email) and
> I got all the automatic tests to pass. I'll be doing more tests before I
> would consider a tag, probably later today.
>
>
> On Mon, Jan 21, 2013 at 10:07 AM, Filip Maj <fil@adobe.com> 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 ci.cordova.io 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.
>>
>>
>

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