Verifies the integrety of the projects, as builds are executed immediately after a code change was detected. This plan provides no artifiacts (use a nightly build instead).

Build: #611 was successful Changes by Florian Schmaus <flo@geekplace.eu>

Build result summary

Details

Completed
Queue duration
4 minutes
Duration
3 minutes
Labels
None
Agent
Default Agent
Revision
04f1d79d720e00aa564f60374f98f033c591d3b8
Total tests
725
Successful since
#607 ()

Tests

Code commits

Author Commit Message Commit date
Florian Schmaus <flo@geekplace.eu> Florian Schmaus <flo@geekplace.eu> 04f1d79d720e00aa564f60374f98f033c591d3b8 Try GC in MemoryLeakTestUtil.assertReferencesQueueSize()
It appears that we observe a partion GC run on some systems,
especially ones with few resources. Hopefully this increases the
chances to observe the expected GC affects so that the unit test
passes also on those systems.
Florian Schmaus <flo@geekplace.eu> Florian Schmaus <flo@geekplace.eu> 2dedd75cd7223859351ce1ebacb6cba2163552fa Add comment about Thread.yield() in MemoryLeakTestUtil