Marked the two known failures as pending. Now everything is green (and
yellow) across the board for UIWebView and WKWebView.

On Tue, Dec 1, 2015 at 11:49 PM, Jesse <purplecabb...@gmail.com> wrote:
>>> Or should I just let it fail still?
> It depends how long it'll be until we fix them.  The build will be broken
> in the CI until it is fixed so probably marking them as pending is the
> better option.
>
>
> @purplecabbage
> risingj.com
>
> On Tue, Dec 1, 2015 at 10:42 PM, Shazron <shaz...@gmail.com> wrote:
>
>> Couldn't wait. All file-transfer specs now pass for uiwebview and
>> wkwebview.
>>
>> For those two WKWebView tests that are failing, but are expected to
>> fail -- I'll try to modify the tests to mark the test as pending if
>> the platform is iOS and the WKWebView bridge is found.
>>
>> Or should I just let it fail still?
>>
>> On Tue, Dec 1, 2015 at 9:49 PM, Shazron <shaz...@gmail.com> wrote:
>> > Thanks! - yeah after I posted it, of course I realized it is all open
>> > source (duh) and I can run a local server or throw it on a
>> > digitalocean instance or something :)
>> > I'll do that tomorrow...
>> >
>> > On Tue, Dec 1, 2015 at 9:24 PM, Carlos Santana <csantan...@gmail.com>
>> wrote:
>> >> For a second I read "the bar is clear", but then I went to my fridge and
>> >> saw I still have some beer left :-)
>> >>
>> >> How long before the INFRA provides the VM for the file transfer, I
>> looked
>> >> the JIRA and it mentioned something like "complete" and "we are in
>> holding
>> >> because of capacity" in the same comment, and I was like stupid because
>> I
>> >> didn't understand :-(
>> >>
>> >> If it's going to take a long time, can we do the test with a local
>> machine
>> >> and vet that it works?
>> >>
>> >> For local xhr loading, I left a comment in the JIRA.  I don't think it's
>> >> need it but I'm curios on how local xhr loading works when fetching
>> normal
>> >> files on a web app, meaning dynamically loading js, css, html in SPA
>> using
>> >> a typical js framework like angular, etc..
>> >>
>> >> Platform API is [5], I think is nice to have but not required for the
>> 4.0
>> >> release.
>> >>
>> >> Oh by the way GREAT PROGRESS !!! and I cheers , I'm having a beer now.
>> >>
>> >>
>> >>
>> >> On Tue, Dec 1, 2015 at 8:38 PM Shazron <shaz...@gmail.com> wrote:
>> >>
>> >>> The board is almost clear [1].
>> >>>
>> >>> UIWebView mobile-spec passes, just waiting for INFRA-10831 [2] for the
>> >>> file-transfer tests.
>> >>> Ditto for WKWebView, it essentially just fails two tests, which are
>> >>> expected [3]
>> >>> (filed a feature request issue [4] for local xhr loading, if needed).
>> >>>
>> >>> Platform API [4] could go in this release as well, what do you think?
>> >>>
>> >>> ---
>> >>>
>> >>> [1] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=76
>> >>> [2] https://issues.apache.org/jira/browse/INFRA-10831
>> >>> [3]
>> >>>
>> https://issues.apache.org/jira/browse/CB-7287?focusedCommentId=15034831&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15034831
>> >>> [4] https://issues.apache.org/jira/browse/CB-10109
>> >>> [5] https://github.com/apache/cordova-ios/pull/176
>> >>>
>> >>> ---------------------------------------------------------------------
>> >>> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
>> >>> For additional commands, e-mail: dev-h...@cordova.apache.org
>> >>>
>> >>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
>> For additional commands, e-mail: dev-h...@cordova.apache.org
>>
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Reply via email to