Global error: TypeError: undefined is not an object (evaluating 'data.length') at http://localhost:7357/assets/test-loader.js, line 115

[briarsweetbriar]

After upgrading from 0.8.0 to 0.9.4, I started getting this error when coverage is enabled:

Global error: TypeError: undefined is not an object (evaluating 'data.length') at http://localhost:7357/assets/test-loader.js, line 115

This may be related to #135, but the issue is not resolved by commit #c992c5efb4d154292a5c04233727a7a282f0e318.

Let me know if there's any additional info that would help.

[jschilli]

does coverage show up in the browser?

On Jun 3, 2016, at 4:37 PM, null null null notifications@github.com wrote:

After upgrading from 0.8.0 to 0.9.4, I started getting this error when coverage is enabled:

Global error: TypeError: undefined is not an object (evaluating 'data.length') at http://localhost:7357/assets/test-loader.js, line 115
This may be related to #135 #135, but the issue is not resolved by commit #c992c5efb4d154292a5c04233727a7a282f0e318.

Let me know if there's any additional info that would help.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub #143, or mute the thread https://github.com/notifications/unsubscribe/AAHejfU-a5F2KPNdAt8wYI2MDAVFiZmXks5qIJCegaJpZM4It4yV.

[briarsweetbriar]

It doesn't.

[jschilli]

Are you running with ?coverage

-jeff

On Jun 3, 2016, at 7:20 PM, null null null notifications@github.com wrote:

It doesn't.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

[briarsweetbriar]

Correct: "test_page": "tests/index.html?hidepassed&coverage"

On Fri, Jun 3, 2016 at 4:23 PM, Jeff Schilling notifications@github.com
wrote:

Are you running with ?coverage

-jeff

On Jun 3, 2016, at 7:20 PM, null null null notifications@github.com
wrote:

It doesn't.

—
You are receiving this because you commented.

Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#143 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/ACk2SAqj1qtK0_Z8XVFv_seBC2iKH5h1ks5qILd5gaJpZM4It4yV
.

[netes]

Same here. This showed up in completely new project with Ember CLI 2.6.2.

[markz1204]

Same problem. When this will be fixed ?

[sglanzer-deprecated]

I don't know about @jschilli, but I personally won't have time to look into this until at least next week - anyone who has time to provide additional debugging information would be appreciated

[bmeurant]

Hi.

I had the same issue with Ember CLI 2.6.2 but it appears that during the update, I also accidentally resolved blanket version to 1.1.7. Rolling back to the original 1.2.1 based fork fixed the issue for me.