(cd run_OMSimulator-cs-cvode && /home/hudson/saved_omc/OMSimulator/install/bin/OMSimulator --resultFile=../ModelicaTest_3.2.3_ModelicaTest.MultiBody.InitializationConversion.Joints_OMSimulator-cs-cvode_res.mat --stripRoot --tempDir=temp_ModelicaTest_3_2_3_ModelicaTest_MultiBody_InitializationConversion_Joints_OMSimulator-cs-cvode_fmu --startTime=0 --stopTime=0.2 --stepSize=3.9984e-05 --mode=cs --timeout=240 --tolerance=1e-06 ../ModelicaTest_3_2_3_ModelicaTest_MultiBody_InitializationConversion_Joints_OMSimulator-cs-cvode.fmu)
LOG_STDOUT        | info    | Using sparse solver for linear system 0,
|                 | |       | because density of 0.016 remains under threshold of 0.200.
LOG_STDOUT        | info    | The simulation runtime does not have access to sparse solvers. Defaulting to a dense linear system solver instead.
LOG_STDOUT        | info    | Using sparse solver for linear system 8,
|                 | |       | because density of 0.017 remains under threshold of 0.200.
LOG_STDOUT        | info    | The simulation runtime does not have access to sparse solvers. Defaulting to a dense linear system solver instead.
LOG_STDOUT        | info    | The maximum density for using sparse solvers can be specified
|                 | |       | using the runtime flag '<-lssMaxDensity=value>'.
LOG_SOLVER        | info    | CVODE linear multistep method CV_BDF
LOG_SOLVER        | info    | CVODE maximum integration order CV_ITER_NEWTON
LOG_SOLVER        | info    | CVODE use equidistant time grid YES
LOG_SOLVER        | info    | CVODE Using relative error tolerance 1.000000e-06
LOG_SOLVER        | info    | CVODE Using dense internal linear solver SUNLinSol_Dense.
LOG_SOLVER        | info    | CVODE Use internal dense numeric jacobian method.
LOG_SOLVER        | info    | CVODE uses internal root finding method NO
LOG_SOLVER        | info    | CVODE maximum absolut step size 0
LOG_SOLVER        | info    | CVODE initial step size is set automatically
LOG_SOLVER        | info    | CVODE maximum integration order 5
LOG_SOLVER        | info    | CVODE maximum number of nonlinear convergence failures permitted during one step 10
LOG_SOLVER        | info    | CVODE BDF stability limit detection algorithm OFF
info: *** FMU Simulation Info ***
     - model     : ModelicaTest.MultiBody.InitializationConversion.Joints (co-simulation)
     - fmiVersion: 2.0
     - startTime : 0.000000
     - stopTime  : 0.200000
     - tolerance : 1e-06
     - stepSize  : 3.9984e-05
info:    Result file: ../ModelicaTest_3.2.3_ModelicaTest.MultiBody.InitializationConversion.Joints_OMSimulator-cs-cvode_res.mat (bufferSize=10)
info:    Parameter Joints.bodyBox.frameTranslation.shapeType will not be stored in the result file, because the signal type is not supported
info:    Parameter Joints.bodyBox1.frameTranslation.shapeType will not be stored in the result file, because the signal type is not supported
info:    Parameter Joints.bodyBox2.frameTranslation.shapeType will not be stored in the result file, because the signal type is not supported
info:    Parameter Joints.bodyBox3.frameTranslation.shapeType will not be stored in the result file, because the signal type is not supported
info:    Parameter Joints.bodyBox4.frameTranslation.shapeType will not be stored in the result file, because the signal type is not supported
info:    Parameter Joints.bodyBox5.frameTranslation.shapeType will not be stored in the result file, because the signal type is not supported
info:    Parameter Joints.bodyBox6.frameTranslation.shapeType will not be stored in the result file, because the signal type is not supported
info:    Parameter Joints.bodyBox7.frameTranslation.shapeType will not be stored in the result file, because the signal type is not supported
info:    Parameter Joints.bodyBox8.frameTranslation.shapeType will not be stored in the result file, because the signal type is not supported
info:    Parameter Joints.world.label1 will not be stored in the result file, because the signal type is not supported
info:    Parameter Joints.world.label2 will not be stored in the result file, because the signal type is not supported