Hmm that is interesting. I always thought that in the case of multiple SLF4J bindings, slf4j will simply pick one of them (first, last, random).
On Thu, May 21, 2015 at 12:34 PM, Stephan Ewen <se...@apache.org> wrote: > The actor system fails to start. Here are the suspicious log lines: > > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in [jar:file:/home/travis/.m2/ > repository/org/slf4j/slf4j-log4j12/1.7.10/slf4j-log4j12- > 1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in [jar:file:/home/travis/build/ > apache/incubator-zeppelin/zeppelin-interpreter/target/ > lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an > explanation. > SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory] > > > Seems that SLF4J has more than one binding. I remember that Akka crashed > because of that before. > > As a simple fix, can you try and exclude the SLF4J jar from your build > somehow? Or set it to "provided" in the Flink POM? > > > > > > On Thu, May 21, 2015 at 11:49 AM, Till Rohrmann <trohrm...@apache.org> > wrote: > > > I'll try to reproduce this problem locally on my machine. > > > > On Thu, May 21, 2015 at 11:25 AM, Fabian Hueske <fhue...@gmail.com> > wrote: > > > > > Hi Flink folks, > > > > > > the Flink interpreter PR for Apache Zeppelin is blocked by a failing > test > > > case (see below). > > > Does anybody have an idea what is going on and can maybe help to > resolve > > > the problem? > > > > > > Thanks, Fabian > > > > > > ---------- Forwarded message ---------- > > > From: Leemoonsoo <g...@git.apache.org> > > > Date: 2015-05-21 6:35 GMT+02:00 > > > Subject: [GitHub] incubator-zeppelin pull request: ZEPPELIN-44 > > Interpreter > > > for Apach... > > > To: d...@zeppelin.incubator.apache.org > > > > > > > > > Github user Leemoonsoo commented on the pull request: > > > > > > > > > > > > https://github.com/apache/incubator-zeppelin/pull/75#issuecomment-104132384 > > > > > > This PR has some test using FlinkMiniCluster. > > > Tests are fine when i run them on my IDE. > > > But if i run them using maven, it fails. (CI is failing, too) > > > > > > I think everything is ready, except for this test failure. Any > advice > > > is very appreciated. > > > here's failure message > > > > > > ``` > > > ------------------------------------------------------- > > > T E S T S > > > ------------------------------------------------------- > > > Running org.apache.zeppelin.flink.FlinkInterpreterTest > > > SLF4J: Class path contains multiple SLF4J bindings. > > > SLF4J: Found binding in > > > > > > > > > [jar:file:/home/travis/.m2/repository/org/slf4j/slf4j-log4j12/1.7.10/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class] > > > SLF4J: Found binding in > > > > > > > > > [jar:file:/home/travis/build/apache/incubator-zeppelin/zeppelin-interpreter/target/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class] > > > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for > an > > > explanation. > > > SLF4J: Actual binding is of type > [org.slf4j.impl.Log4jLoggerFactory] > > > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: > > 106.131 > > > sec <<< FAILURE! - in org.apache.zeppelin.flink.FlinkInterpreterTest > > > org.apache.zeppelin.flink.FlinkInterpreterTest Time elapsed: > 106.131 > > > sec <<< ERROR! > > > java.util.concurrent.TimeoutException: Futures timed out after > > [100000 > > > milliseconds] > > > at > > > scala.concurrent.impl.Promise$DefaultPromise.ready(Promise.scala:219) > > > at > > > scala.concurrent.impl.Promise$DefaultPromise.result(Promise.scala:223) > > > at > > > scala.concurrent.Await$$anonfun$result$1.apply(package.scala:107) > > > at > > > > > > > > > scala.concurrent.BlockContext$DefaultBlockContext$.blockOn(BlockContext.scala:53) > > > at scala.concurrent.Await$.result(package.scala:107) > > > at akka.remote.Remoting.start(Remoting.scala:180) > > > at > > > > akka.remote.RemoteActorRefProvider.init(RemoteActorRefProvider.scala:184) > > > at > > akka.actor.ActorSystemImpl.liftedTree2$1(ActorSystem.scala:619) > > > at > > > akka.actor.ActorSystemImpl._start$lzycompute(ActorSystem.scala:616) > > > at akka.actor.ActorSystemImpl._start(ActorSystem.scala:616) > > > at akka.actor.ActorSystemImpl.start(ActorSystem.scala:633) > > > at akka.actor.ActorSystem$.apply(ActorSystem.scala:142) > > > at akka.actor.ActorSystem$.apply(ActorSystem.scala:119) > > > at akka.actor.ActorSystem$.create(ActorSystem.scala:67) > > > at > > > > > > > > > org.apache.flink.runtime.akka.AkkaUtils$.createActorSystem(AkkaUtils.scala:82) > > > at > > > > > > > > > org.apache.flink.runtime.minicluster.FlinkMiniCluster.startJobManagerActorSystem(FlinkMiniCluster.scala:105) > > > at > > > > > > > > > org.apache.flink.runtime.minicluster.FlinkMiniCluster.<init>(FlinkMiniCluster.scala:61) > > > at > > > > > > > > > org.apache.flink.runtime.minicluster.LocalFlinkMiniCluster.<init>(LocalFlinkMiniCluster.scala:44) > > > at > > > > > > > > > org.apache.zeppelin.flink.FlinkInterpreter.startFlinkMiniCluster(FlinkInterpreter.java:297) > > > at > > > > > > > > > org.apache.zeppelin.flink.FlinkInterpreter.initializeFlinkEnv(FlinkInterpreter.java:152) > > > at > > > > > > org.apache.zeppelin.flink.FlinkInterpreter.open(FlinkInterpreter.java:115) > > > at > > > > > > > > > org.apache.zeppelin.flink.FlinkInterpreterTest.setUp(FlinkInterpreterTest.java:40) > > > > > > > > > Results : > > > > > > Tests in error: > > > FlinkInterpreterTest.setUp:40 » Timeout Futures timed out after > > > [100000 millis... > > > ``` > > > > > > > > > --- > > > If your project is set up for it, you can reply to this email and have > > your > > > reply appear on GitHub as well. If your project does not have this > > feature > > > enabled and wishes so, or if the feature is enabled but not working, > > please > > > contact infrastructure at infrastruct...@apache.org or file a JIRA > > ticket > > > with INFRA. > > > --- > > > > > >
