Orchestrator crashes for TransactionTooLargeException [77752735]

Fixed

Bug

NeedsInfo

Status Update

No update yet.

Description

ri...@soundcloud.com

created issue #1

Apr 10, 2018 09:09AM

Library used (Espresso, Runner, Rules etc.): com.android.support.test:orchestrator
Version used: 1.0.1

How are you running your tests (via Android Studio, Gradle, adb, etc.)?
- Firebase Test Lab (not sure it matters, but we are running 99.99% of our tests there)

How are you running your tests (via Android Studio, Gradle, adb, etc.)?
- gcloud command line

How to reproduce:
- The issue is not happening consistently and I haven't find how to reproduce it.

What is the expected output? What do you see instead?
- I expect to see the test either passed or failed for an assertion failed in my code but I rather get the following error message:

Test instrumentation process crashed. Check com.my.package.MyTest#testName.txt for details.

Reading the logcat I can see this exception printed:

I/TestRunner(8940): ----- begin exception -----
I/TestRunner(8940): java.lang.IllegalStateException: Unable to send TestFailure status, terminating
I/TestRunner(8940): at android.support.test.orchestrator.instrumentationlistener.OrchestratedInstrumentationListener.testFailure(OrchestratedInstrumentationListener.java:136)
I/TestRunner(8940): at org.junit.runner.notification.SynchronizedRunListener.testFailure(SynchronizedRunListener.java:63)
I/TestRunner(8940): at org.junit.runner.notification.RunNotifier$4.notifyListener(RunNotifier.java:142)
I/TestRunner(8940): at org.junit.runner.notification.RunNotifier$SafeNotifier.run(RunNotifier.java:72)
I/TestRunner(8940): at org.junit.runner.notification.RunNotifier.fireTestFailures(RunNotifier.java:138)
I/TestRunner(8940): at org.junit.runner.notification.RunNotifier.fireTestFailure(RunNotifier.java:132)
I/TestRunner(8940): at org.junit.internal.runners.model.EachTestNotifier.addFailure(EachTestNotifier.java:23)
I/TestRunner(8940): at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:329)
I/TestRunner(8940): at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
I/TestRunner(8940): at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
I/TestRunner(8940): at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
I/TestRunner(8940): at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
I/TestRunner(8940): at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
I/TestRunner(8940): at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
I/TestRunner(8940): at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
I/TestRunner(8940): at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
I/TestRunner(8940): at org.junit.runners.Suite.runChild(Suite.java:128)
I/TestRunner(8940): at org.junit.runners.Suite.runChild(Suite.java:27)
I/TestRunner(8940): at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
I/TestRunner(8940): at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
I/TestRunner(8940): at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
I/TestRunner(8940): at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
I/TestRunner(8940): at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
I/TestRunner(8940): at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
I/TestRunner(8940): at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
I/TestRunner(8940): at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
I/TestRunner(8940): at android.support.test.internal.runner.TestExecutor.execute(TestExecutor.java:58)
I/TestRunner(8940): at android.support.test.runner.AndroidJUnitRunner.onStart(AndroidJUnitRunner.java:375)
I/TestRunner(8940): at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1879)
I/TestRunner(8940): Caused by: android.os.TransactionTooLargeException: data parcel size 2495968 bytes
I/TestRunner(8940): at android.os.BinderProxy.transactNative(Native Method)
I/TestRunner(8940): at android.os.BinderProxy.transact(Binder.java:503)
I/TestRunner(8940): at android.support.test.runner.internal.deps.aidl.BaseProxy.transactAndReadExceptionReturnVoid(BaseProxy.java:65)
I/TestRunner(8940): at android.support.test.orchestrator.callback.OrchestratorCallback$Stub$Proxy.sendTestNotification(OrchestratorCallback.java:96)
I/TestRunner(8940): at android.support.test.orchestrator.instrumentationlistener.OrchestratedInstrumentationListener.sendTestNotification(OrchestratedInstrumentationListener.java:167)
I/TestRunner(8940): at android.support.test.orchestrator.instrumentationlistener.OrchestratedInstrumentationListener.testFailure(OrchestratedInstrumentationListener.java:134)
I/TestRunner(8940): ... 28 more
I/TestRunner(8940): ----- end exception -----

Comments

gg...@google.com <gg...@google.com> #2Apr 10, 2018 09:54AM

Assigned to gg...@google.com.

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.

ri...@soundcloud.com <ri...@soundcloud.com> #3Apr 10, 2018 12:23PM

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

nk...@google.com <nk...@google.com> #4Apr 10, 2018 05:02PM

Marked as fixed, 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))

br...@gmail.com <br...@gmail.com> #5Jun 22, 2018 11:44PM

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

[Deleted User] <[Deleted User]> #6Nov 2, 2018 08:07AM

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

[Deleted User] <[Deleted User]> #7Dec 27, 2018 10:53AM

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,

[Deleted User] <[Deleted User]> #8Mar 27, 2019 02:48PM

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.

deleted

Restricted+

0 B

fe...@gmail.com <fe...@gmail.com> #9Jan 29, 2020 02:42PM

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

fe...@gmail.com <fe...@gmail.com> #10Jan 29, 2020 02:45PM

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.

va...@theblueground.com <va...@theblueground.com> #11Apr 4, 2023 10:35AM

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?