Closed eslickj closed 1 year ago
I think I found the issue. The tests that fail seem to have multiple solutions. It seems it's not a problem with Pysmo just that the tests have different equally good results. Here's an example from the first failure. pysmo_test.xlsx
Yeah, I suspected that was the problem given the small size of the training data and the fact that the input variables are strongly correlated. I will probably have to increase the training set size or define a different test problem entirely.
@OOAmusat Any update on this issue? I assume it is not making it into the August release at this point,
@andrewlee94 No updates for now. It'll be addressed, but not before the August release.
@OOAmusat any time soon to get to this?
@ksbeattie Not likely. I think we should probably close this for now
The problem is pretty straight forward and it would be nice if it didn't fail on ARM64. Maybe I can take a little time to see if there is a quick fix to make it so there is unique solution for the test problem.
I think this should be fixed in PR #1070.
Closing as fixed, although we are seeing some random failures for one test case (Kriging) - we suspect that this is due to random sampling which should be fixed.
On both macOS and all Linux distress I tried with ARM64 processors Pysmo tests fails. I can't really see a clear reason by the test output is below.