spark-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Loughran <ste...@hortonworks.com>
Subject Jenkins PR failing, Mima unhappy: bad constant pool tag 50 at byte 12
Date Thu, 31 Mar 2016 11:52:55 GMT

A WiP PR of mine is failing in mima: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54525/consoleFull

[info] spark-examples: previous-artifact not set, not analyzing binary compatibility
java.lang.RuntimeException: bad constant pool tag 50 at byte 12
at com.typesafe.tools.mima.core.ClassfileParser$ConstantPool.errorBadTag(ClassfileParser.scala:204)
at com.typesafe.tools.mima.core.ClassfileParser$ConstantPool.<init>(ClassfileParser.scala:106)
at com.typesafe.tools.mima.core.ClassfileParser.parseAll(ClassfileParser.scala:67)
at com.typesafe.tools.mima.core.ClassfileParser.parse(ClassfileParser.scala:59)
at com.typesafe.tools.mima.core.ClassInfo.ensureLoaded(ClassInfo.scala:86)
at com.typesafe.tools.mima.core.ClassInfo.methods(ClassInfo.scala:101)
at com.typesafe.tools.mima.core.ClassInfo$$anonfun$lookupClassMethods$2.apply(ClassInfo.scala:123)
at com.typesafe.tools.mima.core.ClassInfo$$anonfun$lookupClassMethods$2.apply(ClassInfo.scala:123)

...

That's the kind of message which hints at some kind of JVM versioning mismatch, but, AFAIK,
I'm (a) just pulling in java 6/7 libraries and (b) skipping the hadoop-2.6+ module anyway.

Any suggestions to make the stack trace go away

Mime
View raw message