OMSimulator -r ModelicaTest_3.2.2_fmi_ModelicaTest.MultiBody.Joints.JointUSP2_res.mat --tempDir temp_ModelicaTest_3_2_2_fmi_ModelicaTest_MultiBody_Joints_JointUSP2_fmu --startTime 0 --stopTime 4 --tolerance 1e-06 ModelicaTest_3_2_2_fmi_ModelicaTest_MultiBody_Joints_JointUSP2.fmu
info:    Initializing logging (OMSimulator v0.0.0-204-g82c54af)
info:    new temp directory has been created: "temp_ModelicaTest_3_2_2_fmi_ModelicaTest_MultiBody_Joints_JointUSP2_fmu"
info:    Using "/var/lib/hudson/slave/workspace/OpenModelica_TEST_LIBS/OpenModelicaLibraryTesting/ModelicaTest_3.2.2_fmi_ModelicaTest.MultiBody.Joints.JointUSP2/temp_ModelicaTest_3_2_2_fmi_ModelicaTest_MultiBody_Joints_JointUSP2_fmu/temp_6oVYea" as temp directory for fmu
stdout            | info    | The initialization finished successfully without homotopy method.
info:    Result file: ModelicaTest_3.2.2_fmi_ModelicaTest.MultiBody.Joints.JointUSP2_res.mat
assert            | warning | The following assertion has been violated at time 0.660000
|                 | |       | noEvent(jointUSP.prismatic.k1a > 1e-10)
assert            | error   | 
|                 | |       | Singular position of loop (either no or two analytic solutions;
|                 | |       | the mechanism has lost one-degree-of freedom in this position).
|                 | |       | Try first to use another Modelica.Mechanics.MultiBody.Joints.Assemblies.JointXXX component.
|                 | |       | If this also lead to singular positions, it could be that this
|                 | |       | kinematic loop cannot be solved analytically with a fixed state
|                 | |       | selection. In this case you have to build up the loop with
|                 | |       | basic joints (NO aggregation JointXXX components) and rely on
|                 | |       | dynamic state selection, i.e., during simulation the states will
|                 | |       | be dynamically selected in such a way that in no position a
|                 | |       | degree of freedom is lost.
error:   ME-FMU instance (logFmi2Call): fmi2CompletedIntegratorStep: terminated by an assertion.
fatal:   fmi2_import_completed_integrator_step failed
info:    0 warnings
info:    2 errors
info:    Logging completed properly
info:    Initializing logging (OMSimulator v0.0.0-204-g82c54af)
fatal:   Time measurement is corrupted.