Hi Chris, Posted the test log at :
http://pastebin.com/LFEdfQqX Highlight is that it is timing out, and indeed line 325 of the test is task.awaitMessage. Which seems slightly odd as if there was something badly broken with the instantiation of Kafka and sending messages to/from it wouldn't we expect failures in the samza-kafka tests? On the Wheezy box this is failing every time. Regards Garry -----Original Message----- From: Chris Riccomini [mailto:[email protected]] Sent: 03 March 2014 22:55 To: [email protected] Subject: Re: TestStatefulTask failures Hey Garry, Master successfully tested on my Mac OSX box with: $ ./gradlew clean test Cheers, Chris On 3/3/14 2:49 PM, "Chris Riccomini" <[email protected]> wrote: >Hey Garry, > >Hmm. This is alarming. > >This test is really more of an integration test than a unit test, which >makes it a bit trickier to tell why it's failed. It is, however, >extraordinarily useful in catching a ton of obscure bugs that sneak >through most of the other tests. > >Questions: > >1. What is the error you see in the resulting test logs? >2. Does it ALWAYS fail on your Wheezy box, or just sometimes? > >I will try and re-run on my end. It's working fine on a branch of mine >that was rebased mid-last week, but perhaps something has broken. > >Cheers, >Chris > >On 3/3/14 2:44 PM, "Garry Turkington" <[email protected]> >wrote: > >>Hi guys, >> >>Anyone else having issues doing a clean build of master? I was happily >>doing rebuilds on a repo that I hadn't pulled from origin since >>mid-last week. Then I did a git pull today and I get the following on >>each build >>attempt: >> >>org.apache.samza.test.integration.TestStatefulTask > >>testShouldStartAndRestore FAILED >> java.lang.AssertionError at TestStatefulTask.scala:325 >> >>The slightly curious thing is that if I go do a clone of master on a >>different host (Centos 5.2 64-bit) it builds fine but on my usual >>development VM (Debian Wheezy 64-bit) the above happens. >> >>This could be specific to my environment (not the first time!) but I >>also know there have been changes around state and that specific test >>recently so anyone else seeing odd behaviour? >> >>Thanks >>Garry >> > ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4259 / Virus Database: 3705/7144 - Release Date: 03/03/14
