Tests

[halentin]

• add Tests for FMI2

• Tests missing for fmi2<Set, Get><Boolean, String> because the FMU used for testing doesnt have such variables

• Some Calls throw fmi2StatusWarning because the FMU used for testing doenst have variables with causality=<input, output>

• Typos in src/FMI2/cfunc.jl

[halentin]

• Added Tests for fmi2<Set, Get><Boolean, String> using the IO.fmu from FMIZoo.jl

• Those Tests should pass on all Combinations from the Matrix

• There is a weird bug with fmi2DoStep present that appears with both 32-Bit FMUs:

[Warning][][test_cs]: fmi2DoStep: currentCommunicationPoint = 5.37764e-19, expected last stop time at 0.0078125,
 this indicates a mismatch in the master. Simulation will try to continue.

even though SetupExperiment is called with startTime = 0.0 right before. I suspect it is a Problem with Dymola 32-Bit FMUs
This sometimes leads to failing Tests (only on Julia 1.6 for some reason).
I patched it by not testing fmi2DoStep on 32-Bit Systems, but will have to be investigated further to make 32-Bit CoSimulation FMUs work.

[ThummeTo]

type checks are not necessary (redundant), because we will check for type stable functions in the next release

[ThummeTo]

• Added Tests for fmi2<Set, Get><Boolean, String> using the IO.fmu from FMIZoo.jl

  • Those Tests should pass on all Combinations from the Matrix

  • There is a weird bug with fmi2DoStep present that appears with both 32-Bit FMUs:

[Warning][][test_cs]: fmi2DoStep: currentCommunicationPoint = 5.37764e-19, expected last stop time at 0.0078125,
 this indicates a mismatch in the master. Simulation will try to continue.

even though SetupExperiment is called with startTime = 0.0 right before. I suspect it is a Problem with Dymola 32-Bit FMUs This sometimes leads to failing Tests (only on Julia 1.6 for some reason). I patched it by not testing fmi2DoStep on 32-Bit Systems, but will have to be investigated further to make 32-Bit CoSimulation FMUs work.

no problem, 1.6 will be replace by 1.10 as LTS very soon anyway