[QFJ-826] Maven build is failing on test cases for quickfixj-core when compiling with JDK8 Created: 07/Feb/15  Updated: 02/Apr/15  Resolved: 11/Mar/15

Status: Closed
Project: QuickFIX/J
Component/s: Build
Affects Version/s: 1.5.3
Fix Version/s: 1.6.0

Type: Bug Priority: Minor
Reporter: kammo Assignee: Christoph John
Resolution: Fixed Votes: 0
Labels: None


 Description   

Below test cases are failing and hence whole build is failing.
SessionTest.testStateFlagsAreResetOnLogout
SessionTest.testAcceptorRelogon
SessionTest.testDontCatchErrorsFromCallback
SessionTest.testSimultaneousResendRequests
SessionTest.testResendRequestMsgSeqNum
SessionTest.testSequenceResetStackOverflow

 Comments   
Comment by Christoph John [ 07/Feb/15 ]

Hi, I cannot reproduce this. What exactly did you do? Checked out from github? Which java version are you using?
This is the build on the build server which runs fine: http://www.quickfixj.org:8085/browse/QFJ-GIT

Comment by kammo [ 07/Feb/15 ]

hi Chirs, thx for your comment. I'm using java 8 for compilation and build. I downloaded the code from gihub from below link and master.
https://github.com/quickfix-j/quickfixj
I went to quickfixj-master directory after download and ran "mvn clean install" and it is failing for these 6 test cases.

Comment by Christoph John [ 08/Feb/15 ]

I could reproduce this with JDK8 but currently have no idea what is causing it.

Comment by Christoph John [ 03/Mar/15 ]

Maybe related to this: http://randomallsorts.blogspot.de/2012/12/junit-411-whats-new-test-execution-order.html
(actually introduced by JDK7, but we skipped that)

Comment by Christoph John [ 10/Mar/15 ]

Hi kammo, I cannot really explain this but I cannot reproduce the errors anymore. Looking at the commits I can see nothing obvious what might have fixed it (JUnit upgrade maybe?)
Does it also work for you now with a fresh checkout?

Edit: if it does not work, could you please tell me which exact JDK and Maven version you are using.

Comment by kammo [ 11/Mar/15 ]

it looks fine now. we can close this jira.

Comment by kammo [ 11/Mar/15 ]

Thanks for your help.

Comment by Christoph John [ 11/Mar/15 ]

Strange enough that it works now, but thanks.

Generated at Sat Nov 23 00:24:43 UTC 2024 using JIRA 7.5.2#75007-sha1:9f5725bb824792b3230a5d8716f0c13e296a3cae.