An update (and a nudge)…
So far it's been more than 20 hours, and the tests are still running.
Most tests seem to fail with one of two different errors…
1. Address already in use
cascading.flow.FlowException: [test] unhandled exception
at cascading.flow.BaseFlow.complete(BaseFlow.java:977)
at
cascading.flow.FlowStrategiesPlatformTest.testSkipStrategiesReplace(FlowStrategiesPlatformTest.java:67)
Caused by: org.jboss.netty.channel.ChannelException: Failed to bind to:
/127.0.0.1:6123
at
org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:272)
…
Caused by: java.net.BindException: Address already in use
…
2. FlowStepJob.blockOnJob throws a cascading.flow.FlowException
All caused by a 100 second timeout
Is the above expected?
Thanks,
-- Ken
> From: Ken Krugler
> Sent: March 28, 2016 3:39:12pm PDT
> To: dev@flink.apache.org
> Subject: Expected duration for cascading-flink tests?
>
> Hi all,
>
> I'm curious how long the tests are expected to take for cascading-flink.
>
> I know that https://github.com/dataArtisans/cascading-flink recommends
> running mvn clean install with -DskipTests, but I was going to try updating
> to flink 1.0.0 (currently using 0.10.0) and cascading 3.1.0-wip-56 (currently
> on wip-39), so I wanted to first verify that all tests passed before updating
> and then running the tests again.
>
> In any case, the tests have been running for about 2.5 hours now. From what I
> can tell, it's legit - most of the time is tied to
> cascading.flow.planner.rul.RuleSetExec's call() method.
>
> Maybe this is a sign that it's time for a new Mac :)
>
> Thanks,
>
> -- Ken
>
--------------------------
Ken Krugler
+1 530-210-6378
http://www.scaleunlimited.com
custom big data solutions & training
Hadoop, Cascading, Cassandra & Solr
