when mixing Classes marked with ProblematicTest.class that are SerialClassRunner and ParallelClassRunner Test will not run correctly.
but methods marked ProblematicTest.class that are from classes the are or SerialClassRunner and ParallelClassRunner, seem ok when the tests run in the jenkins job
printing all threads stack trace, is making the console out put very large and not giving much info
Individual methods must be marked as Problematic or the Test wont all run happy together
Merge branch 'master' of https://github.com/hazelcast/hazelcast into Problematic
Fixed exposing of internal array to the enduser
Fixed smaller checkstyle issues in MapReduce
Fixed compile error on last commit
Optimized the getMember functionality so that not every time a new collection
is build. This collection is now build when set and later can be retrieved using
a simple volatile read. Also did some cleanup so that null check is needed
anymore.
Cleanup of NodeMulticastListener
Improved logging
Moved spurious failing and badly written test to the ProblematicSection

NearCacheTest.testNearCacheEvictionByUsingMapTTLEviction
EvictionTest.testEvictionSpeedTestPerPartition
Merge branch 'master' of https://github.com/hazelcast/hazelcast
Adding Missing Spring 4 Cache Method

Spring 4 adds a method with signature:
public <T> T get(Object key, Class<T> type)
Added another flaky time based test to ProblematicTests
Minor repartitioningstresstest cleanup
Removed unneeded nullcheck
Added a hashcode to InstancePermissions
Added more logs to entry listener unittest
Minor cleanup in topic
Executor cleanup