We don't handle failures in @BeforeClass [37057596]

Fixed

Bug

[AOSP] assigned

Migrated-Tools-testing

Status Update

No update yet.

Description

be...@google.com

created issue #1

Aug 20, 2015 03:41PM

Version: TOT

When tests fail to start (for example because of an error in @BeforeClass), gradle gets confused, it only sees missing test results, no stack trace is captured or reported.

Tested with AndroidJUnitRunner.

Comments

ch...@google.com <ch...@google.com> Jan 11, 2016 10:52PM

Assigned to ch...@google.com.

be...@google.com <be...@google.com> Jan 28, 2016 11:52AM

Reassigned to to...@android.com.

zb...@gmail.com <zb...@gmail.com> #2Oct 7, 2016 04:10PM

I have also seen this issue, careful analysis has shown it appears to be related to the canary version of the caf_receiver framework.

In debug mode you will see: Load failed: cast.o.media.Il.create is not a function

This function appears to be missing in

https://www.gstatic.com/cast/sdk/libs/caf_receiver/canary/cast_receiver_framework.js, the code in the non-canary framework, located at

https://www.gstatic.com/cast/sdk/libs/caf_receiver/v3/cast_receiver_framework.js doesn't have this issue.

zb...@gmail.com <zb...@gmail.com> #3Jun 9, 2017 02:25PM

I'm having this issue with 1 of my 3 Chromecasts and actually bought a new Chromecast because I thought it was broken.

be...@google.com <be...@google.com> #4Jun 22, 2017 03:31PM

Reassigned to nk...@google.com.

Hi There,

I am also experiencing this issue. I have 9 chromecasts V3, all bought at the same time and on 2 of them I was not able to cast images using either the
default or styled media reciever.
When comparing the debugs of a working and non working device I found that the non working one is using the canary framework instead of the V3

First of all i checked and this device doesn't have the Preview program on, how come it gets beta code ?

The error is as stated above on the cast.o.media.Il.create function

Non working canary
c = c.startsWith("image/") ? cast.o.media.Il.create(b) : .L(new hu(b,ku))

Working V3
c = c.startsWith("image/") ? .K(new ot(b)) : _.K(new Nt(b,Qt))

xa...@google.com <xa...@google.com> #5Jul 28, 2017 04:39AM

Thanks for reporting the issue. We will investigate further and get back to you with our findings.

nk...@google.com <nk...@google.com> #6Jul 28, 2017 05:01PM

Thanks for reporting the issue. We will investigate further and get back to you with our findings.

Can you also confirm whether this is happening with our latest version? You can try the preview URL that can be found here:

https://developers.google.com/cast/preview-url

xa...@google.com <xa...@google.com> #7Jul 28, 2017 05:02PM

Hello,

So I created a custom reciever app pointing to the preview cast reciever version and I have the same error

https://www.gstatic.com/cast/sdk/libs/caf_receiver/preview/cast_receiver_framework.js
It looks like the bug is also present in the preview version.

The problem I have is even if I specify to use the v3 cast reciever (

https://www.gstatic.com/cast/sdk/libs/caf_receiver/v3/cast_receiver_framework.js) in my custom reciver app in the debbugs is see the chromecast using the canary library (

https://www.gstatic.com/cast/sdk/libs/caf_receiver/canary/cast_receiver_framework.js) ... Why?

Why this chromecast in particular has this behavior ?
serial number is: 1125ADSFDMJ

Is there another version of the cast_receiver_framework.js that i could use ?

Thanks,

nk...@google.com <nk...@google.com> Aug 12, 2017 12:31AM

Reassigned to am...@google.com.

zb...@gmail.com <zb...@gmail.com> #8Feb 22, 2018 11:12AM

Can you please confirm if this preview version is the same one announced on [Feb 10th (https://groups.google.com/g/cast-sdk-announcements/c/-dLdTPHTvDc) that is now in canary testing?

There are disconnects between the dates in the announcement channel and the release notes this year, alignment seems to be be better in Nov/Dec last year.

be...@google.com <be...@google.com> #9Feb 22, 2018 11:17AM

Reassigned to sl...@google.com.

Hello,

The SDK version is CAST SDK CAF Version: 3.0.0095 the shaka player loaded is 3.0.10. So apparently not the same as the one announced on Feb 10th (3.0.8).
I attached the whole debug output with the preview framework (

https://www.gstatic.com/cast/sdk/libs/caf_receiver/preview/cast_receiver_framework.js)

How come some devices use canary and some do not ?

Thanks,

Joris

sl...@google.com <sl...@google.com> Mar 21, 2018 04:52PM

Status: New

br...@google.com <br...@google.com> #10Mar 27, 2018 10:47PM

To answer your questions, as we roll out the releases, some devices will see the new release (canary) and others will see the old release until the new release is fully ramped up in production. In Feb we found an issue with Shaka player version 3.0.8 which was fixed in version 3.0.10. We delayed the rollout of the receiver release to get the updated Shaka player 3.0.10 into the release, and that's what's currently in canary (and in preview). (The preview URL will always point to the newest build about to be released.)

For the cssting photos bug reported here, engineering has implemented a fix, and we hope to update the release with the fix tomorrow. We'll do our best to update this bug as soon as the fix is in canary.

nk...@google.com <nk...@google.com> Apr 5, 2018 10:12PM

Assigned to nk...@google.com.

nk...@google.com <nk...@google.com> #11Apr 6, 2018 09:48PM

Marked as fixed.

We're in the process of updating the preview URL with the fix, which should be in place in an hour or so. Joris or John, once that's in place, would you be able to do quick check against the preview URL with the development version of your apps to verify that this has fixed the problems reported?