You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Ian Clelland <ic...@chromium.org> on 2014/08/25 22:09:41 UTC
[Testing] No content to speak of
The dev list has been almost silent since Friday PM; maybe I'm just
paranoid after the last outage, but I want to see if this gets through.
Sorry for the noise, everyone can go back to making Cordova awesome now :)
Ian
Re: [Testing] No content to speak of
Posted by Marcel Kinard <cm...@gmail.com>.
(waves hand)
This isn't the content you are looking for.
;-)
On Aug 25, 2014, at 4:23 PM, Ian Clelland <ic...@chromium.org> wrote:
> Hey! What are you doing hijacking my content-free thread?
>
> :)
>
> I haven't seen that, but I haven't run mobilespec in a while either. I'll
> check it out and see if I can reproduce it.
>
> Usually an empty yellow box on startup means that the bridge isn't working,
> but if you're seeing ~300 other successful tests, then that's unlikely to
> be the problem.
>
> Ian
Re: [Testing] No content to speak of
Posted by Ian Clelland <ic...@chromium.org>.
Looks like it started failing with 0ffb969 (Fixes multiple mobilespec tests
errors). There's a lot in there; I'll have to take that commit apart now to
figure out what happened. I wrote the original tests, though, so I know
what it *should* be doing, at least.
I'll re-open https://issues.apache.org/jira/browse/CB-6148.
Thanks for the heads-up, Marcel.
Ian
On Mon, Aug 25, 2014 at 4:49 PM, Ian Clelland <ic...@chromium.org>
wrote:
> :)
>
> I do see the failures in the latest master. It was working as recently as
> the 1.3.0 release, so I'm bisecting right now.
>
>
>
> On Mon, Aug 25, 2014 at 4:45 PM, Josh Soref <js...@blackberry.com> wrote:
>
>> Ian Clelland wrote:
>> > Hey! What are you doing hijacking my content-free thread?
>>
>> > I haven't seen that, but I haven't run mobilespec in a while either.
>>
>> I've only run createmobilespec itself recently, I haven't actually *used*
>> mobile-spec :)
>>
>>
>
Re: [Testing] No content to speak of
Posted by Ian Clelland <ic...@chromium.org>.
:)
I do see the failures in the latest master. It was working as recently as
the 1.3.0 release, so I'm bisecting right now.
On Mon, Aug 25, 2014 at 4:45 PM, Josh Soref <js...@blackberry.com> wrote:
> Ian Clelland wrote:
> > Hey! What are you doing hijacking my content-free thread?
>
> > I haven't seen that, but I haven't run mobilespec in a while either.
>
> I've only run createmobilespec itself recently, I haven't actually *used*
> mobile-spec :)
>
>
Re: [Testing] No content to speak of
Posted by Josh Soref <js...@blackberry.com>.
Ian Clelland wrote:
> Hey! What are you doing hijacking my content-free thread?
> I haven't seen that, but I haven't run mobilespec in a while either.
I've only run createmobilespec itself recently, I haven't actually *used*
mobile-spec :)
Re: [Testing] No content to speak of
Posted by Carlos Santana <cs...@gmail.com>.
Hey I thought this was a free content thread.
$ ping cordova.io
On Mon, Aug 25, 2014 at 7:51 PM, Jesse <pu...@gmail.com> wrote:
> Okay, thanks all, I am digging in now too for wp8, and windows, I don't
> think that change was intentional in Entry.js, but I'll see soon.
>
> Moving the rest of conversation to CB-7375
> <https://issues.apache.org/jira/browse/CB-7375>, This thread was meant to
> test communication, which has passed.
>
> @purplecabbage
> risingj.com
>
>
> On Mon, Aug 25, 2014 at 4:46 PM, Martin Gonzalez <
> martin.c.glez.glez@gmail.com> wrote:
>
> > The reason of this fails as Ian pointed out are the references to the
> > filesystem on the entry.
> > 125 Expected --> FileSystem: persistent ; Returned :temporary
> > 126 Expected --> FileSystem: temporary ; Returned :persistent
> > 127 Expected --> FileSystem: persistent ; Returned :temporary
> > 128 Expected --> FileSystem: temporary ; Returned :persistent
> >
> > I've got this results, getting the filesystem property from the entry.
> >
> > I've created an issue related to this subject, in order to fix it for all
> > platforms.
> > https://issues.apache.org/jira/browse/CB-7375
> >
> >
> >
> > 2014-08-25 18:31 GMT-05:00 Ian Clelland <ic...@chromium.org>:
> >
> > > The changes to Entry.js introduce this failure; for some reason the
> > > reference to entry.filesystemName was replaced with
> > entry.filesystem.name,
> > > and so the entry is not being returned with a reference to the correct
> > > filesystem.
> > >
> > > I think that this was a change made to accommodate Windows Phone, which
> > > broke Android (and probably iOS). There's a fundamental difference
> > between
> > > how we have to pass the filesystem object across the bridge vs. how we
> > can
> > > pass it around in JavaScript, and this change makes one style work, at
> > the
> > > expense of the other.
> > >
> > > I'll see this evening if I can work up a version that will work for
> both,
> > > and get some WP8 testers to look at it in the morning.
> > >
> > > Ian
> > >
> > >
> > > On Mon, Aug 25, 2014 at 7:06 PM, Jesse <pu...@gmail.com>
> wrote:
> > >
> > > > Which tests are now failing, what do they test, and how have you
> > verified
> > > > that they should pass? Just because they used to pass, does not mean
> > they
> > > > are valid, or should have passed.
> > > >
> > > > This change to DirectoryEntry.js makes perfect sense, and may have
> > > > uncovered a previously passing test that should have failed.
> > > >
> > > > - if (!/\/$/.test(nativeURL)) {
> > > > + if (nativeURL && !/\/$/.test(nativeURL)) {
> > > > nativeURL += "/";
> > > > }
> > > >
> > > > Similarily, the changes to www/resolveLocalFileSystemURI.js and
> > > > www/Entry.js do not appear to introduce a new failure, but could be
> > > > uncovering previously falsely passing test(s)
> > > >
> > > >
> > > >
> > > > @purplecabbage
> > > > risingj.com
> > > >
> > > >
> > > > On Mon, Aug 25, 2014 at 3:56 PM, Martin Gonzalez <
> > > > martin.c.glez.glez@gmail.com> wrote:
> > > >
> > > > > The tests shouldn't be failing. I agree with Ian, the tests started
> > to
> > > > fail
> > > > > after:
> > > > > 0ffb969 (Fixes multiple mobilespec tests
> > > > > errors). I've verified with the previous commit and everything
> works
> > as
> > > > > expected.
> > > > > On Aug 25, 2014 5:46 PM, "Jesse" <pu...@gmail.com> wrote:
> > > > >
> > > > > > I was just noting a possible reason for the tests to now fail.
> > > > > > Has anyone verified whether they should fail or not?
> > > > > >
> > > > > > @purplecabbage
> > > > > > risingj.com
> > > > > >
> > > > > >
> > > > > > On Mon, Aug 25, 2014 at 3:27 PM, Michal Mocny <
> mmocny@chromium.org
> > >
> > > > > wrote:
> > > > > >
> > > > > > > The 4 failing file tests were reported on JIRA (
> > > > > > > https://issues.apache.org/jira/browse/CB-7093) and I thought
> > > > > > Martin/Jesse
> > > > > > > were looking at them.
> > > > > > >
> > > > > > >
> > > > > > > On Mon, Aug 25, 2014 at 5:39 PM, Marcel Kinard <
> > cmarcelk@gmail.com
> > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > > Yes, all the other automated tests (except the 4 File tests
> as
> > > > > > previously
> > > > > > > > noted) are running successfully, so that does seem to point
> > > > somewhere
> > > > > > > else
> > > > > > > > besides the bridge.
> > > > > > > >
> > > > > > > > The issue appears to be related to CB-6764. If I remove from
> > > > > > > mobile-spec's
> > > > > > > > index.html the script reference to
> "doesnotexist/notcordova.js"
> > > > then
> > > > > > the
> > > > > > > > device object and the yellow box gets populated properly.
> > > > > > > >
> > > > > > > > On Aug 25, 2014, at 4:23 PM, Ian Clelland <
> > > iclelland@chromium.org>
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Usually an empty yellow box on startup means that the
> bridge
> > > > isn't
> > > > > > > > working,
> > > > > > > > > but if you're seeing ~300 other successful tests, then
> that's
> > > > > > unlikely
> > > > > > > to
> > > > > > > > > be the problem.
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> >
> >
> > --
> > Regards,
> > Martin Gonzalez
> >
>
--
Carlos Santana
<cs...@gmail.com>
Re: [Testing] No content to speak of
Posted by Jesse <pu...@gmail.com>.
Okay, thanks all, I am digging in now too for wp8, and windows, I don't
think that change was intentional in Entry.js, but I'll see soon.
Moving the rest of conversation to CB-7375
<https://issues.apache.org/jira/browse/CB-7375>, This thread was meant to
test communication, which has passed.
@purplecabbage
risingj.com
On Mon, Aug 25, 2014 at 4:46 PM, Martin Gonzalez <
martin.c.glez.glez@gmail.com> wrote:
> The reason of this fails as Ian pointed out are the references to the
> filesystem on the entry.
> 125 Expected --> FileSystem: persistent ; Returned :temporary
> 126 Expected --> FileSystem: temporary ; Returned :persistent
> 127 Expected --> FileSystem: persistent ; Returned :temporary
> 128 Expected --> FileSystem: temporary ; Returned :persistent
>
> I've got this results, getting the filesystem property from the entry.
>
> I've created an issue related to this subject, in order to fix it for all
> platforms.
> https://issues.apache.org/jira/browse/CB-7375
>
>
>
> 2014-08-25 18:31 GMT-05:00 Ian Clelland <ic...@chromium.org>:
>
> > The changes to Entry.js introduce this failure; for some reason the
> > reference to entry.filesystemName was replaced with
> entry.filesystem.name,
> > and so the entry is not being returned with a reference to the correct
> > filesystem.
> >
> > I think that this was a change made to accommodate Windows Phone, which
> > broke Android (and probably iOS). There's a fundamental difference
> between
> > how we have to pass the filesystem object across the bridge vs. how we
> can
> > pass it around in JavaScript, and this change makes one style work, at
> the
> > expense of the other.
> >
> > I'll see this evening if I can work up a version that will work for both,
> > and get some WP8 testers to look at it in the morning.
> >
> > Ian
> >
> >
> > On Mon, Aug 25, 2014 at 7:06 PM, Jesse <pu...@gmail.com> wrote:
> >
> > > Which tests are now failing, what do they test, and how have you
> verified
> > > that they should pass? Just because they used to pass, does not mean
> they
> > > are valid, or should have passed.
> > >
> > > This change to DirectoryEntry.js makes perfect sense, and may have
> > > uncovered a previously passing test that should have failed.
> > >
> > > - if (!/\/$/.test(nativeURL)) {
> > > + if (nativeURL && !/\/$/.test(nativeURL)) {
> > > nativeURL += "/";
> > > }
> > >
> > > Similarily, the changes to www/resolveLocalFileSystemURI.js and
> > > www/Entry.js do not appear to introduce a new failure, but could be
> > > uncovering previously falsely passing test(s)
> > >
> > >
> > >
> > > @purplecabbage
> > > risingj.com
> > >
> > >
> > > On Mon, Aug 25, 2014 at 3:56 PM, Martin Gonzalez <
> > > martin.c.glez.glez@gmail.com> wrote:
> > >
> > > > The tests shouldn't be failing. I agree with Ian, the tests started
> to
> > > fail
> > > > after:
> > > > 0ffb969 (Fixes multiple mobilespec tests
> > > > errors). I've verified with the previous commit and everything works
> as
> > > > expected.
> > > > On Aug 25, 2014 5:46 PM, "Jesse" <pu...@gmail.com> wrote:
> > > >
> > > > > I was just noting a possible reason for the tests to now fail.
> > > > > Has anyone verified whether they should fail or not?
> > > > >
> > > > > @purplecabbage
> > > > > risingj.com
> > > > >
> > > > >
> > > > > On Mon, Aug 25, 2014 at 3:27 PM, Michal Mocny <mmocny@chromium.org
> >
> > > > wrote:
> > > > >
> > > > > > The 4 failing file tests were reported on JIRA (
> > > > > > https://issues.apache.org/jira/browse/CB-7093) and I thought
> > > > > Martin/Jesse
> > > > > > were looking at them.
> > > > > >
> > > > > >
> > > > > > On Mon, Aug 25, 2014 at 5:39 PM, Marcel Kinard <
> cmarcelk@gmail.com
> > >
> > > > > wrote:
> > > > > >
> > > > > > > Yes, all the other automated tests (except the 4 File tests as
> > > > > previously
> > > > > > > noted) are running successfully, so that does seem to point
> > > somewhere
> > > > > > else
> > > > > > > besides the bridge.
> > > > > > >
> > > > > > > The issue appears to be related to CB-6764. If I remove from
> > > > > > mobile-spec's
> > > > > > > index.html the script reference to "doesnotexist/notcordova.js"
> > > then
> > > > > the
> > > > > > > device object and the yellow box gets populated properly.
> > > > > > >
> > > > > > > On Aug 25, 2014, at 4:23 PM, Ian Clelland <
> > iclelland@chromium.org>
> > > > > > wrote:
> > > > > > >
> > > > > > > > Usually an empty yellow box on startup means that the bridge
> > > isn't
> > > > > > > working,
> > > > > > > > but if you're seeing ~300 other successful tests, then that's
> > > > > unlikely
> > > > > > to
> > > > > > > > be the problem.
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
>
>
> --
> Regards,
> Martin Gonzalez
>
Re: [Testing] No content to speak of
Posted by Martin Gonzalez <ma...@gmail.com>.
The reason of this fails as Ian pointed out are the references to the
filesystem on the entry.
125 Expected --> FileSystem: persistent ; Returned :temporary
126 Expected --> FileSystem: temporary ; Returned :persistent
127 Expected --> FileSystem: persistent ; Returned :temporary
128 Expected --> FileSystem: temporary ; Returned :persistent
I've got this results, getting the filesystem property from the entry.
I've created an issue related to this subject, in order to fix it for all
platforms.
https://issues.apache.org/jira/browse/CB-7375
2014-08-25 18:31 GMT-05:00 Ian Clelland <ic...@chromium.org>:
> The changes to Entry.js introduce this failure; for some reason the
> reference to entry.filesystemName was replaced with entry.filesystem.name,
> and so the entry is not being returned with a reference to the correct
> filesystem.
>
> I think that this was a change made to accommodate Windows Phone, which
> broke Android (and probably iOS). There's a fundamental difference between
> how we have to pass the filesystem object across the bridge vs. how we can
> pass it around in JavaScript, and this change makes one style work, at the
> expense of the other.
>
> I'll see this evening if I can work up a version that will work for both,
> and get some WP8 testers to look at it in the morning.
>
> Ian
>
>
> On Mon, Aug 25, 2014 at 7:06 PM, Jesse <pu...@gmail.com> wrote:
>
> > Which tests are now failing, what do they test, and how have you verified
> > that they should pass? Just because they used to pass, does not mean they
> > are valid, or should have passed.
> >
> > This change to DirectoryEntry.js makes perfect sense, and may have
> > uncovered a previously passing test that should have failed.
> >
> > - if (!/\/$/.test(nativeURL)) {
> > + if (nativeURL && !/\/$/.test(nativeURL)) {
> > nativeURL += "/";
> > }
> >
> > Similarily, the changes to www/resolveLocalFileSystemURI.js and
> > www/Entry.js do not appear to introduce a new failure, but could be
> > uncovering previously falsely passing test(s)
> >
> >
> >
> > @purplecabbage
> > risingj.com
> >
> >
> > On Mon, Aug 25, 2014 at 3:56 PM, Martin Gonzalez <
> > martin.c.glez.glez@gmail.com> wrote:
> >
> > > The tests shouldn't be failing. I agree with Ian, the tests started to
> > fail
> > > after:
> > > 0ffb969 (Fixes multiple mobilespec tests
> > > errors). I've verified with the previous commit and everything works as
> > > expected.
> > > On Aug 25, 2014 5:46 PM, "Jesse" <pu...@gmail.com> wrote:
> > >
> > > > I was just noting a possible reason for the tests to now fail.
> > > > Has anyone verified whether they should fail or not?
> > > >
> > > > @purplecabbage
> > > > risingj.com
> > > >
> > > >
> > > > On Mon, Aug 25, 2014 at 3:27 PM, Michal Mocny <mm...@chromium.org>
> > > wrote:
> > > >
> > > > > The 4 failing file tests were reported on JIRA (
> > > > > https://issues.apache.org/jira/browse/CB-7093) and I thought
> > > > Martin/Jesse
> > > > > were looking at them.
> > > > >
> > > > >
> > > > > On Mon, Aug 25, 2014 at 5:39 PM, Marcel Kinard <cmarcelk@gmail.com
> >
> > > > wrote:
> > > > >
> > > > > > Yes, all the other automated tests (except the 4 File tests as
> > > > previously
> > > > > > noted) are running successfully, so that does seem to point
> > somewhere
> > > > > else
> > > > > > besides the bridge.
> > > > > >
> > > > > > The issue appears to be related to CB-6764. If I remove from
> > > > > mobile-spec's
> > > > > > index.html the script reference to "doesnotexist/notcordova.js"
> > then
> > > > the
> > > > > > device object and the yellow box gets populated properly.
> > > > > >
> > > > > > On Aug 25, 2014, at 4:23 PM, Ian Clelland <
> iclelland@chromium.org>
> > > > > wrote:
> > > > > >
> > > > > > > Usually an empty yellow box on startup means that the bridge
> > isn't
> > > > > > working,
> > > > > > > but if you're seeing ~300 other successful tests, then that's
> > > > unlikely
> > > > > to
> > > > > > > be the problem.
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
--
Regards,
Martin Gonzalez
Re: [Testing] No content to speak of
Posted by Ian Clelland <ic...@chromium.org>.
The changes to Entry.js introduce this failure; for some reason the
reference to entry.filesystemName was replaced with entry.filesystem.name,
and so the entry is not being returned with a reference to the correct
filesystem.
I think that this was a change made to accommodate Windows Phone, which
broke Android (and probably iOS). There's a fundamental difference between
how we have to pass the filesystem object across the bridge vs. how we can
pass it around in JavaScript, and this change makes one style work, at the
expense of the other.
I'll see this evening if I can work up a version that will work for both,
and get some WP8 testers to look at it in the morning.
Ian
On Mon, Aug 25, 2014 at 7:06 PM, Jesse <pu...@gmail.com> wrote:
> Which tests are now failing, what do they test, and how have you verified
> that they should pass? Just because they used to pass, does not mean they
> are valid, or should have passed.
>
> This change to DirectoryEntry.js makes perfect sense, and may have
> uncovered a previously passing test that should have failed.
>
> - if (!/\/$/.test(nativeURL)) {
> + if (nativeURL && !/\/$/.test(nativeURL)) {
> nativeURL += "/";
> }
>
> Similarily, the changes to www/resolveLocalFileSystemURI.js and
> www/Entry.js do not appear to introduce a new failure, but could be
> uncovering previously falsely passing test(s)
>
>
>
> @purplecabbage
> risingj.com
>
>
> On Mon, Aug 25, 2014 at 3:56 PM, Martin Gonzalez <
> martin.c.glez.glez@gmail.com> wrote:
>
> > The tests shouldn't be failing. I agree with Ian, the tests started to
> fail
> > after:
> > 0ffb969 (Fixes multiple mobilespec tests
> > errors). I've verified with the previous commit and everything works as
> > expected.
> > On Aug 25, 2014 5:46 PM, "Jesse" <pu...@gmail.com> wrote:
> >
> > > I was just noting a possible reason for the tests to now fail.
> > > Has anyone verified whether they should fail or not?
> > >
> > > @purplecabbage
> > > risingj.com
> > >
> > >
> > > On Mon, Aug 25, 2014 at 3:27 PM, Michal Mocny <mm...@chromium.org>
> > wrote:
> > >
> > > > The 4 failing file tests were reported on JIRA (
> > > > https://issues.apache.org/jira/browse/CB-7093) and I thought
> > > Martin/Jesse
> > > > were looking at them.
> > > >
> > > >
> > > > On Mon, Aug 25, 2014 at 5:39 PM, Marcel Kinard <cm...@gmail.com>
> > > wrote:
> > > >
> > > > > Yes, all the other automated tests (except the 4 File tests as
> > > previously
> > > > > noted) are running successfully, so that does seem to point
> somewhere
> > > > else
> > > > > besides the bridge.
> > > > >
> > > > > The issue appears to be related to CB-6764. If I remove from
> > > > mobile-spec's
> > > > > index.html the script reference to "doesnotexist/notcordova.js"
> then
> > > the
> > > > > device object and the yellow box gets populated properly.
> > > > >
> > > > > On Aug 25, 2014, at 4:23 PM, Ian Clelland <ic...@chromium.org>
> > > > wrote:
> > > > >
> > > > > > Usually an empty yellow box on startup means that the bridge
> isn't
> > > > > working,
> > > > > > but if you're seeing ~300 other successful tests, then that's
> > > unlikely
> > > > to
> > > > > > be the problem.
> > > > >
> > > > >
> > > >
> > >
> >
>
Re: [Testing] No content to speak of
Posted by Jesse <pu...@gmail.com>.
Which tests are now failing, what do they test, and how have you verified
that they should pass? Just because they used to pass, does not mean they
are valid, or should have passed.
This change to DirectoryEntry.js makes perfect sense, and may have
uncovered a previously passing test that should have failed.
- if (!/\/$/.test(nativeURL)) {
+ if (nativeURL && !/\/$/.test(nativeURL)) {
nativeURL += "/";
}
Similarily, the changes to www/resolveLocalFileSystemURI.js and
www/Entry.js do not appear to introduce a new failure, but could be
uncovering previously falsely passing test(s)
@purplecabbage
risingj.com
On Mon, Aug 25, 2014 at 3:56 PM, Martin Gonzalez <
martin.c.glez.glez@gmail.com> wrote:
> The tests shouldn't be failing. I agree with Ian, the tests started to fail
> after:
> 0ffb969 (Fixes multiple mobilespec tests
> errors). I've verified with the previous commit and everything works as
> expected.
> On Aug 25, 2014 5:46 PM, "Jesse" <pu...@gmail.com> wrote:
>
> > I was just noting a possible reason for the tests to now fail.
> > Has anyone verified whether they should fail or not?
> >
> > @purplecabbage
> > risingj.com
> >
> >
> > On Mon, Aug 25, 2014 at 3:27 PM, Michal Mocny <mm...@chromium.org>
> wrote:
> >
> > > The 4 failing file tests were reported on JIRA (
> > > https://issues.apache.org/jira/browse/CB-7093) and I thought
> > Martin/Jesse
> > > were looking at them.
> > >
> > >
> > > On Mon, Aug 25, 2014 at 5:39 PM, Marcel Kinard <cm...@gmail.com>
> > wrote:
> > >
> > > > Yes, all the other automated tests (except the 4 File tests as
> > previously
> > > > noted) are running successfully, so that does seem to point somewhere
> > > else
> > > > besides the bridge.
> > > >
> > > > The issue appears to be related to CB-6764. If I remove from
> > > mobile-spec's
> > > > index.html the script reference to "doesnotexist/notcordova.js" then
> > the
> > > > device object and the yellow box gets populated properly.
> > > >
> > > > On Aug 25, 2014, at 4:23 PM, Ian Clelland <ic...@chromium.org>
> > > wrote:
> > > >
> > > > > Usually an empty yellow box on startup means that the bridge isn't
> > > > working,
> > > > > but if you're seeing ~300 other successful tests, then that's
> > unlikely
> > > to
> > > > > be the problem.
> > > >
> > > >
> > >
> >
>
Re: [Testing] No content to speak of
Posted by Martin Gonzalez <ma...@gmail.com>.
The tests shouldn't be failing. I agree with Ian, the tests started to fail
after:
0ffb969 (Fixes multiple mobilespec tests
errors). I've verified with the previous commit and everything works as
expected.
On Aug 25, 2014 5:46 PM, "Jesse" <pu...@gmail.com> wrote:
> I was just noting a possible reason for the tests to now fail.
> Has anyone verified whether they should fail or not?
>
> @purplecabbage
> risingj.com
>
>
> On Mon, Aug 25, 2014 at 3:27 PM, Michal Mocny <mm...@chromium.org> wrote:
>
> > The 4 failing file tests were reported on JIRA (
> > https://issues.apache.org/jira/browse/CB-7093) and I thought
> Martin/Jesse
> > were looking at them.
> >
> >
> > On Mon, Aug 25, 2014 at 5:39 PM, Marcel Kinard <cm...@gmail.com>
> wrote:
> >
> > > Yes, all the other automated tests (except the 4 File tests as
> previously
> > > noted) are running successfully, so that does seem to point somewhere
> > else
> > > besides the bridge.
> > >
> > > The issue appears to be related to CB-6764. If I remove from
> > mobile-spec's
> > > index.html the script reference to "doesnotexist/notcordova.js" then
> the
> > > device object and the yellow box gets populated properly.
> > >
> > > On Aug 25, 2014, at 4:23 PM, Ian Clelland <ic...@chromium.org>
> > wrote:
> > >
> > > > Usually an empty yellow box on startup means that the bridge isn't
> > > working,
> > > > but if you're seeing ~300 other successful tests, then that's
> unlikely
> > to
> > > > be the problem.
> > >
> > >
> >
>
Re: [Testing] No content to speak of
Posted by Jesse <pu...@gmail.com>.
I was just noting a possible reason for the tests to now fail.
Has anyone verified whether they should fail or not?
@purplecabbage
risingj.com
On Mon, Aug 25, 2014 at 3:27 PM, Michal Mocny <mm...@chromium.org> wrote:
> The 4 failing file tests were reported on JIRA (
> https://issues.apache.org/jira/browse/CB-7093) and I thought Martin/Jesse
> were looking at them.
>
>
> On Mon, Aug 25, 2014 at 5:39 PM, Marcel Kinard <cm...@gmail.com> wrote:
>
> > Yes, all the other automated tests (except the 4 File tests as previously
> > noted) are running successfully, so that does seem to point somewhere
> else
> > besides the bridge.
> >
> > The issue appears to be related to CB-6764. If I remove from
> mobile-spec's
> > index.html the script reference to "doesnotexist/notcordova.js" then the
> > device object and the yellow box gets populated properly.
> >
> > On Aug 25, 2014, at 4:23 PM, Ian Clelland <ic...@chromium.org>
> wrote:
> >
> > > Usually an empty yellow box on startup means that the bridge isn't
> > working,
> > > but if you're seeing ~300 other successful tests, then that's unlikely
> to
> > > be the problem.
> >
> >
>
Re: [Testing] No content to speak of
Posted by Michal Mocny <mm...@chromium.org>.
The 4 failing file tests were reported on JIRA (
https://issues.apache.org/jira/browse/CB-7093) and I thought Martin/Jesse
were looking at them.
On Mon, Aug 25, 2014 at 5:39 PM, Marcel Kinard <cm...@gmail.com> wrote:
> Yes, all the other automated tests (except the 4 File tests as previously
> noted) are running successfully, so that does seem to point somewhere else
> besides the bridge.
>
> The issue appears to be related to CB-6764. If I remove from mobile-spec's
> index.html the script reference to "doesnotexist/notcordova.js" then the
> device object and the yellow box gets populated properly.
>
> On Aug 25, 2014, at 4:23 PM, Ian Clelland <ic...@chromium.org> wrote:
>
> > Usually an empty yellow box on startup means that the bridge isn't
> working,
> > but if you're seeing ~300 other successful tests, then that's unlikely to
> > be the problem.
>
>
Re: [Testing] No content to speak of
Posted by Ian Clelland <ic...@chromium.org>.
I'll check that out; the file changes could be related to my commits
yesterday
On Wed, Aug 27, 2014 at 10:58 AM, Edna Y Morales <ey...@us.ibm.com>
wrote:
> I'm seeing many many failing iOS tests. They are seen across file,
> file-transfer, globalization, geolocation, and media with timeout and
> reference errors mostly. Can anyone else verify this or is it just me?
>
> Thanks,
> Edna Morales
>
> [image: Inactive hide details for "Sergey Grebnov (Akvelon)" ---08/27/2014
> 09:39:45 AM---Vladimir Kotikov and me will join this testing]"Sergey
> Grebnov (Akvelon)" ---08/27/2014 09:39:45 AM---Vladimir Kotikov and me will
> join this testing party soon and help with the testing and necessary im
>
> From: "Sergey Grebnov (Akvelon)" <v-...@microsoft.com>
> To: "dev@cordova.apache.org" <de...@cordova.apache.org>
> Date: 08/27/2014 09:39 AM
> Subject: RE: [Testing] No content to speak of
> ------------------------------
>
>
>
> Vladimir Kotikov and me will join this testing party soon and help with
> the testing and necessary improvements(if any). Currently we see some
> problem with dynamic manual tests generation (at least in Camera tests) on
> Windows due to special unsafe html restrictions on this platform, Vladimir
> will send details and workaround.
>
> Thx!
> Sergey
> -----Original Message-----
> From: Martin Gonzalez [mailto:martin.c.glez.glez@gmail.com
> <ma...@gmail.com>]
> Sent: Wednesday, August 27, 2014 5:12 PM
> To: dev@cordova.apache.org
> Subject: Re: [Testing] No content to speak of
>
> Agree, over android it looks good, however running the tests over Windows
> Phone, the final count is 13 new fails.
> Specs failing: 9, 9.5, 10, 11, 15, 24, 82, 110, 116, 121, 122, 123, 124.
>
>
>
> 2014-08-26 11:20 GMT-05:00 Marcel Kinard <cm...@gmail.com>:
>
> > Thanks, Ian! On Android 4.4, I'm now getting no failures with the all
> > the automatic tests (new-style plugin tests and old-style non-plugin
> tests).
> >
> > Now to start poking at the manual tests...
> >
> > On Aug 26, 2014, at 11:27 AM, Ian Clelland <ic...@chromium.org>
> wrote:
> >
> > > The other issue should be resolved now, but if someone with a WP8
> > > device can test it out as well, it'd be appreciated.
> >
> >
>
>
> --
> Regards,
> Martin Gonzalez
>
>
RE: [Testing] No content to speak of
Posted by Edna Y Morales <ey...@us.ibm.com>.
I'm seeing many many failing iOS tests. They are seen across file,
file-transfer, globalization, geolocation, and media with timeout and
reference errors mostly. Can anyone else verify this or is it just me?
Thanks,
Edna Morales
From: "Sergey Grebnov (Akvelon)" <v-...@microsoft.com>
To: "dev@cordova.apache.org" <de...@cordova.apache.org>
Date: 08/27/2014 09:39 AM
Subject: RE: [Testing] No content to speak of
Vladimir Kotikov and me will join this testing party soon and help with the
testing and necessary improvements(if any). Currently we see some problem
with dynamic manual tests generation (at least in Camera tests) on Windows
due to special unsafe html restrictions on this platform, Vladimir will
send details and workaround.
Thx!
Sergey
-----Original Message-----
From: Martin Gonzalez [mailto:martin.c.glez.glez@gmail.com]
Sent: Wednesday, August 27, 2014 5:12 PM
To: dev@cordova.apache.org
Subject: Re: [Testing] No content to speak of
Agree, over android it looks good, however running the tests over Windows
Phone, the final count is 13 new fails.
Specs failing: 9, 9.5, 10, 11, 15, 24, 82, 110, 116, 121, 122, 123, 124.
2014-08-26 11:20 GMT-05:00 Marcel Kinard <cm...@gmail.com>:
> Thanks, Ian! On Android 4.4, I'm now getting no failures with the all
> the automatic tests (new-style plugin tests and old-style non-plugin
tests).
>
> Now to start poking at the manual tests...
>
> On Aug 26, 2014, at 11:27 AM, Ian Clelland <ic...@chromium.org>
wrote:
>
> > The other issue should be resolved now, but if someone with a WP8
> > device can test it out as well, it'd be appreciated.
>
>
--
Regards,
Martin Gonzalez
RE: [Testing] No content to speak of
Posted by "Sergey Grebnov (Akvelon)" <v-...@microsoft.com>.
Vladimir Kotikov and me will join this testing party soon and help with the testing and necessary improvements(if any). Currently we see some problem with dynamic manual tests generation (at least in Camera tests) on Windows due to special unsafe html restrictions on this platform, Vladimir will send details and workaround.
Thx!
Sergey
-----Original Message-----
From: Martin Gonzalez [mailto:martin.c.glez.glez@gmail.com]
Sent: Wednesday, August 27, 2014 5:12 PM
To: dev@cordova.apache.org
Subject: Re: [Testing] No content to speak of
Agree, over android it looks good, however running the tests over Windows Phone, the final count is 13 new fails.
Specs failing: 9, 9.5, 10, 11, 15, 24, 82, 110, 116, 121, 122, 123, 124.
2014-08-26 11:20 GMT-05:00 Marcel Kinard <cm...@gmail.com>:
> Thanks, Ian! On Android 4.4, I'm now getting no failures with the all
> the automatic tests (new-style plugin tests and old-style non-plugin tests).
>
> Now to start poking at the manual tests...
>
> On Aug 26, 2014, at 11:27 AM, Ian Clelland <ic...@chromium.org> wrote:
>
> > The other issue should be resolved now, but if someone with a WP8
> > device can test it out as well, it'd be appreciated.
>
>
--
Regards,
Martin Gonzalez
Re: [Testing] No content to speak of
Posted by Martin Gonzalez <ma...@gmail.com>.
Agree, over android it looks good, however running the tests over Windows
Phone, the final count is 13 new fails.
Specs failing: 9, 9.5, 10, 11, 15, 24, 82, 110, 116, 121, 122, 123, 124.
2014-08-26 11:20 GMT-05:00 Marcel Kinard <cm...@gmail.com>:
> Thanks, Ian! On Android 4.4, I'm now getting no failures with the all the
> automatic tests (new-style plugin tests and old-style non-plugin tests).
>
> Now to start poking at the manual tests...
>
> On Aug 26, 2014, at 11:27 AM, Ian Clelland <ic...@chromium.org> wrote:
>
> > The other issue should be resolved now, but if someone with a WP8 device
> > can test it out as well, it'd be appreciated.
>
>
--
Regards,
Martin Gonzalez
Re: [Testing] No content to speak of
Posted by Marcel Kinard <cm...@gmail.com>.
Thanks, Ian! On Android 4.4, I'm now getting no failures with the all the automatic tests (new-style plugin tests and old-style non-plugin tests).
Now to start poking at the manual tests...
On Aug 26, 2014, at 11:27 AM, Ian Clelland <ic...@chromium.org> wrote:
> The other issue should be resolved now, but if someone with a WP8 device
> can test it out as well, it'd be appreciated.
Re: [Testing] No content to speak of
Posted by Ian Clelland <ic...@chromium.org>.
The other issue should be resolved now, but if someone with a WP8 device
can test it out as well, it'd be appreciated.
On Tue, Aug 26, 2014 at 9:04 AM, Marcel Kinard <cm...@gmail.com> wrote:
> I figured out why the values for device.* weren't getting set causing the
> yellow box in mobile-spec to be mostly empty. Self-inflicted mistake on my
> side. Please disregard.
>
> On Aug 25, 2014, at 5:39 PM, Marcel Kinard <cm...@gmail.com> wrote:
>
> > Yes, all the other automated tests (except the 4 File tests as
> previously noted) are running successfully, so that does seem to point
> somewhere else besides the bridge.
> >
> > The issue appears to be related to CB-6764. If I remove from
> mobile-spec's index.html the script reference to
> "doesnotexist/notcordova.js" then the device object and the yellow box gets
> populated properly.
> >
> > On Aug 25, 2014, at 4:23 PM, Ian Clelland <ic...@chromium.org>
> wrote:
> >
> >> Usually an empty yellow box on startup means that the bridge isn't
> working,
> >> but if you're seeing ~300 other successful tests, then that's unlikely
> to
> >> be the problem.
> >
>
>
Re: [Testing] No content to speak of
Posted by Marcel Kinard <cm...@gmail.com>.
I figured out why the values for device.* weren't getting set causing the yellow box in mobile-spec to be mostly empty. Self-inflicted mistake on my side. Please disregard.
On Aug 25, 2014, at 5:39 PM, Marcel Kinard <cm...@gmail.com> wrote:
> Yes, all the other automated tests (except the 4 File tests as previously noted) are running successfully, so that does seem to point somewhere else besides the bridge.
>
> The issue appears to be related to CB-6764. If I remove from mobile-spec's index.html the script reference to "doesnotexist/notcordova.js" then the device object and the yellow box gets populated properly.
>
> On Aug 25, 2014, at 4:23 PM, Ian Clelland <ic...@chromium.org> wrote:
>
>> Usually an empty yellow box on startup means that the bridge isn't working,
>> but if you're seeing ~300 other successful tests, then that's unlikely to
>> be the problem.
>
Re: [Testing] No content to speak of
Posted by Marcel Kinard <cm...@gmail.com>.
Yes, all the other automated tests (except the 4 File tests as previously noted) are running successfully, so that does seem to point somewhere else besides the bridge.
The issue appears to be related to CB-6764. If I remove from mobile-spec's index.html the script reference to "doesnotexist/notcordova.js" then the device object and the yellow box gets populated properly.
On Aug 25, 2014, at 4:23 PM, Ian Clelland <ic...@chromium.org> wrote:
> Usually an empty yellow box on startup means that the bridge isn't working,
> but if you're seeing ~300 other successful tests, then that's unlikely to
> be the problem.
Re: [Testing] No content to speak of
Posted by Ian Clelland <ic...@chromium.org>.
Hey! What are you doing hijacking my content-free thread?
:)
I haven't seen that, but I haven't run mobilespec in a while either. I'll
check it out and see if I can reproduce it.
Usually an empty yellow box on startup means that the bridge isn't working,
but if you're seeing ~300 other successful tests, then that's unlikely to
be the problem.
Ian
On Mon, Aug 25, 2014 at 4:19 PM, Marcel Kinard <cm...@gmail.com> wrote:
> Yup, has been quiet.
>
> BTW, speaking of testing, I'm running mobile-spec against master on
> Android 4.4.4 and seeing:
> - 4 failures in File automatic tests:
> - file.spec.125
> - file.spec.126
> - file.spec.127
> - file.spec.128
> - the "device" object isn't getting set with values upon startup, so the
> yellow box is mostly empty
>
> Anyone else seeing this?
>
> On Aug 25, 2014, at 4:14 PM, Ian Clelland <ic...@chromium.org> wrote:
>
> > Well, I'm glad somebody's out there ;)
>
>
Re: [Testing] No content to speak of
Posted by Marcel Kinard <cm...@gmail.com>.
Yup, has been quiet.
BTW, speaking of testing, I'm running mobile-spec against master on Android 4.4.4 and seeing:
- 4 failures in File automatic tests:
- file.spec.125
- file.spec.126
- file.spec.127
- file.spec.128
- the "device" object isn't getting set with values upon startup, so the yellow box is mostly empty
Anyone else seeing this?
On Aug 25, 2014, at 4:14 PM, Ian Clelland <ic...@chromium.org> wrote:
> Well, I'm glad somebody's out there ;)
Re: [Testing] No content to speak of
Posted by Michal Mocny <mm...@chromium.org>.
I've done more work in 2 days than in 2 weeks. Coincidence?...
On Mon, Aug 25, 2014 at 4:14 PM, Ian Clelland <ic...@chromium.org>
wrote:
> Well, I'm glad somebody's out there ;)
>
> Thanks
> Ian
>
>
> On Mon, Aug 25, 2014 at 4:11 PM, Jesse <pu...@gmail.com> wrote:
>
> > I was starting to wonder the same ...
> > Seems it is just quiet!
> >
> > @purplecabbage
> > risingj.com
> >
> >
> > On Mon, Aug 25, 2014 at 1:09 PM, Ian Clelland <ic...@chromium.org>
> > wrote:
> >
> > > The dev list has been almost silent since Friday PM; maybe I'm just
> > > paranoid after the last outage, but I want to see if this gets through.
> > >
> > > Sorry for the noise, everyone can go back to making Cordova awesome now
> > :)
> > >
> > > Ian
> > >
> >
>
Re: [Testing] No content to speak of
Posted by Ian Clelland <ic...@chromium.org>.
Well, I'm glad somebody's out there ;)
Thanks
Ian
On Mon, Aug 25, 2014 at 4:11 PM, Jesse <pu...@gmail.com> wrote:
> I was starting to wonder the same ...
> Seems it is just quiet!
>
> @purplecabbage
> risingj.com
>
>
> On Mon, Aug 25, 2014 at 1:09 PM, Ian Clelland <ic...@chromium.org>
> wrote:
>
> > The dev list has been almost silent since Friday PM; maybe I'm just
> > paranoid after the last outage, but I want to see if this gets through.
> >
> > Sorry for the noise, everyone can go back to making Cordova awesome now
> :)
> >
> > Ian
> >
>
Re: [Testing] No content to speak of
Posted by Jesse <pu...@gmail.com>.
I was starting to wonder the same ...
Seems it is just quiet!
@purplecabbage
risingj.com
On Mon, Aug 25, 2014 at 1:09 PM, Ian Clelland <ic...@chromium.org>
wrote:
> The dev list has been almost silent since Friday PM; maybe I'm just
> paranoid after the last outage, but I want to see if this gets through.
>
> Sorry for the noise, everyone can go back to making Cordova awesome now :)
>
> Ian
>