Due to an an issue with python compilations across different processing architectures and floating point calculations we where hitting an extreme edge case where Scipy returning a slightly different decimal which throws off the tests when rounded. This seems to be solved by just swapping around the targets that we are optimizing
Changelog
Explanation
Due to an an issue with python compilations across different processing architectures and floating point calculations we where hitting an extreme edge case where Scipy returning a slightly different decimal which throws off the tests when rounded. This seems to be solved by just swapping around the targets that we are optimizing