-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prepare v0.12.3 #314
Prepare v0.12.3 #314
Conversation
Zeitsperre
commented
Oct 2, 2023
•
edited
Loading
edited
8961237
to
6858aea
Compare
@@ -375,6 +375,7 @@ | |||
|
|||
|
|||
@pytest.mark.slow | |||
@pytest.mark.xfail(reason="SpotPy Calibration is not entirely stable.") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is quite weird though. What kind of instabilities are we talking about ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is one of the tests that "sometimes" fails, regardless of build environment. There are a handful of tests that are not threadsafe, but because they kill the pytest workers when they fail, there's no way to mark them as xfailable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wouldn't be surprised if the failures are due to the longstanding libnetcdf issues with asynchronous read of NetCDF4 files.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.