[
https://issues.apache.org/jira/browse/STORM-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14096834#comment-14096834
]
Mark Mandel edited comment on STORM-426 at 8/14/14 10:37 AM:
-------------------------------------------------------------
After running all the tests via REPL, the issues with Clojure 1.6 seem
restricted to the `storm-core` module.
There are two levels here:
*Maven Install*
There are some timing issues with Maven Install that seem to cause services to
be shut down before the event-manager (src/clj/backtype/storm/event.clj) to be
shut down, causing it to error.
Strangely enough, I seem to have solved this my placing some more logging in
the event-manager, which seems to work, as disturbing as that is.
*Transactional Tests*
The other issues seem confined to the Transactional Tests
(test/clj/backtype/storm/transactional_test.clj), primarily any of the tests
using `tracked-wait`, as that assertion fails almost all the time.
Again, I seem to have resolved some of the issues by printing extra values, but
that doesn't feel like a real solution at this stage.
For some reason, all the storm-core tests are now working again. I'm getting
very afraid of all the different timing / race condition issues that could
exist in this test suite.
You can see my work here: https://github.com/markmandel/incubator-storm
was (Author: markmandel):
After running all the tests via REPL, the issues with Clojure 1.6 seem
restricted to the `storm-core` module.
There are two levels here:
*Maven Install*
There are some timing issues with Maven Install that seem to cause services to
be shut down before the event-manager (src/clj/backtype/storm/event.clj) to be
shut down, causing it to error.
Strangely enough, I seem to have solved this my placing some more logging in
the event-manager, which seems to work, as disturbing as that is.
*Transactional Tests*
The other issues seem confined to the Transactional Tests
(test/clj/backtype/storm/transactional_test.clj), primarily any of the tests
using `tracked-wait`, as that assertion fails almost all the time.
Again, I seem to have resolved some of the issues by printing extra values, but
that doesn't feel like a real solution at this stage.
For some reason, all the storm-core tests are now working again. I'm getting
very afraid of all the different timing / race condition issues that could
exist in this test suite.
> Upgrade to Clojure 1.6
> ----------------------
>
> Key: STORM-426
> URL: https://issues.apache.org/jira/browse/STORM-426
> Project: Apache Storm (Incubating)
> Issue Type: Improvement
> Affects Versions: 0.9.2-incubating
> Reporter: Mark Mandel
> Attachments: logs.zip
>
>
> It would be very nice if it was possible to use Clojure 1.6 with Storm.
> I'm currently testing it at the moment, and the storm-core tests fail, but
> I'm struggling to narrow down exactly what the issue is.
> With three runs of {{mvn install}} on storm-core, I get 3 different
> issues/exceptions.
> * A FileNotFoundException (test1.log)
> * The tests hang and never complete (test2.log)
> * A report that 'There were some failures', but I struggle to find where
> exactly the failure is amongst all the log files. (test3.log)
> I've attached the test logs in question.
> For reference I also included master.log to show my results when running
> tests against master.
> To determine the issues, I have run each of the tests individually from the
> REPL.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
