Major Receiving log in console: "FATAL: Log statements out of sync: current test case was null" when running unit tests in Jenkins build for iOS project. The build continues and eventually passes, but this error causes build to hang for at least a minute. Our builds now take around 10 minutes instead of the 2 they were taking before.
[JENKINS-37072] Jenkins iOS Build Error - FATAL: Log statements out of sync: current test case was null"
Magnus Lindstedt
added a comment - I agree, we have the same problem:
"FATAL: Log statements out of sync: current test case was null"
This occurs also on XCode plugin 1.4.9 and it doesn't seem fixed on newer versions 1.4.11
There seems to be a person who has made his own fork to solve the problem when the message says:
”DEBUG: Log statements out of sync”, i.e DEBUG instead of FATAL...
http://stackoverflow.com/a/15725083
I haven't tested this though, but anyone here on Jenkins support can maybe take a look at the solution.
Magnus Lindstedt
added a comment - I agree, we have the same problem:
"FATAL: Log statements out of sync: current test case was null"
This occurs also on XCode plugin 1.4.9 and it doesn't seem fixed on newer versions 1.4.11
There seems to be a person who has made his own fork to solve the problem when the message says:
”DEBUG: Log statements out of sync”, i.e DEBUG instead of FATAL...
http://stackoverflow.com/a/15725083
I haven't tested this though, but anyone here on Jenkins support can maybe take a look at the solution. The problem for us seemed to be that we have two threads doing prints during our unittests.
First we have a logging framework called SwiftyBeaver that prints on a background thread, but some other prints in the unittests are made on the main thread and this seems to cause the problem.
So by instead logging all prints to a file, instead of printing, we managed to get away from this bug.
Magnus Lindstedt
added a comment - - edited The problem for us seemed to be that we have two threads doing prints during our unittests.
First we have a logging framework called SwiftyBeaver that prints on a background thread, but some other prints in the unittests are made on the main thread and this seems to cause the problem.
So by instead logging all prints to a file, instead of printing, we managed to get away from this bug. 
Balazs Galambos
added a comment - We are still experiencing the same problem with xcode plugin v2.0.0 and Jenkins ver. 1.642.4.
The JUnit reports which are produced by the plugin are not too useful. Approx 70% of the cases, the diagram is wrong.
It is a major issue for us! Please fix! 
Balazs Galambos
added a comment - We are still experiencing the same problem with xcode plugin v2.0.0 and Jenkins ver. 1.642.4.
The JUnit reports which are produced by the plugin are not too useful. Approx 70% of the cases, the diagram is wrong.
It is a major issue for us! Please fix! I submitted a PR #95 to github with a modification that seems to be related to this article.
Please someone use snapshots and check the problem is solved.
I see same issue in my automated tests. Can this be fixed ASAP please as it makes out tests useless. We get no useful metrics out of out tests because they almost always end with this FATAL error exception. We have over 1000 tests that are run on a daily basis and sometimes it crashes after only 50 tests run. Sometimes it get's almost to the end. There is no pattern in crashing. It's always on a different test/testClass