Seems that 19.0.1 fixes this issue for me, can you check if it solved
your problem as well?

On Fri, Nov 8, 2013 at 9:54 PM, Dan Osipov <[email protected]> wrote:
> Yes, I'm using the latest ADT (v19). I've seen the number of bytes anywhere
> between 4 and 24, in multiples of 4.
>
> Thanks for the pointer - I'll try to downgrade!
>
>
> On Friday, November 8, 2013 3:15:00 PM UTC-5, Andrzej Giniewicz wrote:
>>
>> I've seen similar issue, by any chance you are using Android Build
>> Tools version 19? I had same problem with them, and downgrade to 18.x
>> worked for me. Just to be sure, this no of bytes seems to be pretty
>> random with minor trivial code changes for me, I usually seen 8 or 16
>> bytes (and sometimes it passes).
>>
>> On Fri, Nov 8, 2013 at 7:45 PM, Dan Osipov <[email protected]> wrote:
>> > Hello,
>> >
>> > I'm running sbt clean start to compile a very bare-bones android
>> > application. Some times the operation completes successfully, but most
>> > of
>> > the time I get the following error upon dexing:
>> >
>> > [info] Dexing
>> >
>> > /Users/dano/Documents/android-actors/target/classes-androidactors-compile-0.1.dex
>> >
>> > trouble writing output: excess write of 24
>> > java.lang.RuntimeException: Nonzero exit value: 2
>> > at scala.sys.package$.error(package.scala:27)
>> > at scala.Predef$.error(Predef.scala:123)
>> > at sbt.AbstractProcessBuilder.getString(ProcessImpl.scala:144)
>> > at sbt.AbstractProcessBuilder.$bang$bang(ProcessImpl.scala:146)
>> > at
>> >
>> > sbtandroid.AndroidInstall$$anonfun$dxTask$1$$anonfun$dexing$1$3.apply(AndroidInstall.scala:90)
>> > at
>> >
>> > sbtandroid.AndroidInstall$$anonfun$dxTask$1$$anonfun$dexing$1$3.apply(AndroidInstall.scala:90)
>> > at sbt.MultiLogger.log(MultiLogger.scala:31)
>> > at sbt.Logger$class.debug(Logger.scala:112)
>> > at sbt.AbstractLogger.debug(Logger.scala:11)
>> > at
>> >
>> > sbtandroid.AndroidInstall$$anonfun$dxTask$1.dexing$1(AndroidInstall.scala:90)
>> > at
>> >
>> > sbtandroid.AndroidInstall$$anonfun$dxTask$1.apply(AndroidInstall.scala:111)
>> > at
>> >
>> > sbtandroid.AndroidInstall$$anonfun$dxTask$1.apply(AndroidInstall.scala:67)
>> > at sbt.Scoped$$anonfun$hf11$1.apply(Structure.scala:587)
>> > at sbt.Scoped$$anonfun$hf11$1.apply(Structure.scala:587)
>> > at scala.Function1$$anonfun$compose$1.apply(Function1.scala:49)
>> > at
>> >
>> > sbt.Scoped$Reduced$$anonfun$combine$1$$anonfun$apply$12.apply(Structure.scala:311)
>> > at
>> >
>> > sbt.Scoped$Reduced$$anonfun$combine$1$$anonfun$apply$12.apply(Structure.scala:311)
>> > at sbt.$tilde$greater$$anonfun$$u2219$1.apply(TypeFunctions.scala:41)
>> > at sbt.std.Transform$$anon$5.work(System.scala:71)
>> > at
>> > sbt.Execute$$anonfun$submit$1$$anonfun$apply$1.apply(Execute.scala:232)
>> > at
>> > sbt.Execute$$anonfun$submit$1$$anonfun$apply$1.apply(Execute.scala:232)
>> > at sbt.ErrorHandling$.wideConvert(ErrorHandling.scala:18)
>> > at sbt.Execute.work(Execute.scala:238)
>> > at sbt.Execute$$anonfun$submit$1.apply(Execute.scala:232)
>> > at sbt.Execute$$anonfun$submit$1.apply(Execute.scala:232)
>> > at
>> >
>> > sbt.ConcurrentRestrictions$$anon$4$$anonfun$1.apply(ConcurrentRestrictions.scala:160)
>> > at sbt.CompletionService$$anon$2.call(CompletionService.scala:30)
>> > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>> > at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>> > at
>> > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
>> > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>> > at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>> > at
>> >
>> > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>> > at
>> >
>> > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>> > at java.lang.Thread.run(Thread.java:680)
>> > [error] (compile:dx) Nonzero exit value: 2
>> >
>> > Nothing changes in the source between failed and successful runs, so the
>> > error is very random, and there is no solid way to replicate it. Has
>> > anyone
>> > else experienced it? Anything I can do to trace it?
>> > FYI: I filed a bug about this problem here:
>> > https://github.com/jberkel/android-plugin/issues/197
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> > Groups
>> > "scala-on-android" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> > an
>> > email to [email protected].
>> > For more options, visit https://groups.google.com/groups/opt_out.
>
> --
> You received this message because you are subscribed to the Google Groups
> "scala-on-android" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.

-- 
You received this message because you are subscribed to the Google Groups 
"scala-on-android" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to