Closed wohlbier closed 3 years ago
I haven't seen this error yet in any of my tests for v1.0.0. I also haven't gotten this exception for any tests of the current pull request that should be done before the end of this week (v1.1.0).
Are you just profiling in this case? Or are there other tools included in this test?
Yes, that was profiling. It was resolved by switching to the dev branch. I didn't look at the diffs between the dev branch vs the 1.0.0 at the time, but whatever they were they fixed the issue.
Hi, which branch should we be using for evaluation. I'm running into a numerical exception and wondering if I should pull from your dev branch.