Experimental code that gets tested every 20 minutes on the Jenkins server.
Given how much development I have done the past week on the introduction of a new dynamic component configuration management engine, life cycle management and a new readings engine for Hydra - I need to have continuous testing.
Good way to find deadlocks too, other than the two methods I do when I want to formally verify the system is good:
1. Draw an interaction graph to know who holds what locks (so far I have a roughly good idea that all locking is uni-directional)
2. There are actually tools for this (in the case you missed point 1), JConsole has deadlock detection (mutual exclusions are the ones I care to find)