The added exceptions (#233) have revealed that the 1dtube tests are currently crashing due discrepancies in the output.
It turns out that the line numbers of certain functions have changed between referenceOutput and output, e.g
(0) 07:39:57 [impl::SolverInterfaceImpl]:272 in initialize: [0mit 1 of 40 | dt# 1 | t 0 of 1 | dt 0.01 | max dt 0.01 | ongoing yes | dt complete no | write-iteration-checkpoint |
(0) 16:22:15 [impl::SolverInterfaceImpl]:264 in initialize: [0mit 1 of 40 | dt# 1 | t 0 of 1 | dt 0.01 | max dt 0.01 | ongoing yes | dt complete no | write-iteration-checkpoint |
which the comparison script picks up on. Since this is not a breaking change, the text filter in the script has been appended to ignore such line numbers.
The added exceptions (#233) have revealed that the 1dtube tests are currently crashing due discrepancies in the output.
It turns out that the line numbers of certain functions have changed between referenceOutput and output, e.g
which the comparison script picks up on. Since this is not a breaking change, the text filter in the script has been appended to ignore such line numbers.