ahh hit send accidently.  I'm not sure which tests are causing the
exception shown....I'm still learning the codebase


On Wed, Aug 20, 2014 at 12:06 AM, Naresh Kosgi <[email protected]>
wrote:

> Harsha,
>
> Here is my stack trace from mvn clean install:
>
> java.lang.RuntimeException: backtype.storm.multilang.NoOutputException:
> Pipe to subprocess seems to be broken! No output read.
> Serializer Exception:
> (Unable to capture error stream)
>
>         at
> backtype.storm.utils.ShellProcess.readShellMsg(ShellProcess.java:101)
> ~[classes/:na]
>         at backtype.storm.task.ShellBolt$1.run(ShellBolt.java:115)
> ~[classes/:na]
>         at java.lang.Thread.run(Thread.java:744) [na:1.7.0_51]
> 58848 [Thread-516-disruptor-executor[4 4]-send-queue] INFO
>  backtype.storm.util - Async loop interrupted!
> 58848
> [Thread-517-__metricsclojure.storm.metric.testing.FakeMetricConsumer] INFO
>  backtype.storm.util - Async loop interrupted!
> 58848 [Thread-514] ERROR backtype.storm.daemon.executor -
> java.lang.RuntimeException: backtype.storm.multilang.NoOutputException:
> Pipe to subprocess seems to be broken! No output read.
> Serializer Exception:
> (Unable to capture error stream)
>
>         at
> backtype.storm.utils.ShellProcess.readShellMsg(ShellProcess.java:101)
> ~[classes/:na]
>         at backtype.storm.task.ShellBolt$1.run(ShellBolt.java:115)
> ~[classes/:na]
>         at java.lang.Thread.run(Thread.java:744) [na:1.7.0_51]
> 58848 [main] INFO  backtype.storm.daemon.executor - Shut down executor
> __metricsclojure.storm.metric.testing.FakeMetricConsumer:[4 4]
> 58848 [main] INFO  backtype.storm.daemon.executor - Shutting down executor
> __system:[-1 -1]
> 58848 [Thread-518-disruptor-executor[-1 -1]-send-queue] INFO
>  backtype.storm.util - Async loop interrupted!
> 58848 [Thread-519-__system] INFO  backtype.storm.util - Async loop
> interrupted!
> 58849 [main] INFO  backtype.storm.daemon.executor - Shut down executor
> __system:[-1 -1]
> 58849 [main] INFO  backtype.storm.daemon.executor - Shutting down executor
> 1:[1 1]
> 58849 [Thread-521-1] INFO  backtype.storm.util - Async loop interrupted!
> 58849 [Thread-520-disruptor-executor[1 1]-send-queue] INFO
>  backtype.storm.util - Async loop interrupted!
> 58849 [main] INFO  backtype.storm.daemon.executor - Shut down executor
> 1:[1 1]
> 58849 [main] INFO  backtype.storm.daemon.worker - Shut down executors
> 58849 [main] INFO  backtype.storm.daemon.worker - Shutting down transfer
> thread
> 58849 [Thread-523-disruptor-worker-transfer-queue] INFO
>  backtype.storm.util - Async loop interrupted!
> 58849 [main] INFO  backtype.storm.daemon.worker - Shut down transfer thread
> 58850 [main] INFO  backtype.storm.daemon.worker - Shutting down default
> resources
> 58850 [main] INFO  backtype.storm.daemon.worker - Shut down default
> resources
> 58851 [main] INFO  backtype.storm.daemon.worker - Disconnecting from storm
> cluster state context
> 58851 [main] INFO  backtype.storm.daemon.worker - Shut down worker
> shell-metrics-tester-1-6 202660b1-b8eb-4b6f-af26-5ab80faee13c 1024
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Storm ............................................. SUCCESS [
>  1.460 s]
> [INFO] maven-shade-clojure-transformer ................... SUCCESS [
>  1.533 s]
> [INFO] Storm Core ........................................ FAILURE [01:13
> min]
> [INFO] storm-starter ..................................... SKIPPED
> [INFO] storm-kafka ....................................... SKIPPED
> [INFO] storm-hdfs ........................................ SKIPPED
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 01:17 min
> [INFO] Finished at: 2014-08-20T00:05:29-05:00
> [INFO] Final Memory: 35M/588M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> com.theoryinpractise:clojure-maven-plugin:1.3.18:test-with-junit
> (test-clojure) on project storm-core: Clojure failed. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn <goals> -rf :storm-core
>
>
> On Tue, Aug 19, 2014 at 11:48 PM, Harsha <[email protected]> wrote:
>
>> Taylor,
>>      I ran tests on the latest changes didn't see any failures but did
>>      notice some connection timeouts they didn't result in tests
>>      failing.
>>
>> Naresh,
>>      It might be related to something else. Can you please share you
>>      environment and which tests are failing.
>> Thanks,
>> Harsha
>>
>> On Tue, Aug 19, 2014, at 08:28 PM, Naresh Kosgi wrote:
>> > yes, I can only get the project to build when I ignore the tests.
>> >
>> > mvn clean install does not work for me.  I have to use mvn clean install
>> > -DskipTests.
>> >
>> >
>> > On Tue, Aug 19, 2014 at 11:05 PM, P. Taylor Goetz <[email protected]>
>> > wrote:
>> >
>> > > I’m seeing seemingly non-deterministic test failures in the master
>> branch
>> > > (namely test timeouts)
>> > >
>> > > Is anyone else seeing that? Do we need to revert some commits?
>> > >
>> > > - Taylor
>> > >
>>
>
>

Reply via email to