You are going to have to upgrade to JMockit 1.5 to avoid this problem.
It occurs because of JMockit's inability to work in the presence of Robolectric's AsmInstrumentingClassLoader
. Version 1.5 of JMockit makes it more robust in environments with custom classloading.