-
Notifications
You must be signed in to change notification settings - Fork 62
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
pytest annoyances and intermittent segfault #1067
Comments
I tried fixing these by suppressing the destructor in some previous commits. I've been unable to determine how exactly these are being called in such a way where I can stop these errors from appearing on the CI tests. |
Most of them are due to caching on top of caching that are not release. Some, if not all, are not needed b/c the underlying slow/"called multiple times" function is already cached upstream. I'd love a speed test to be 100% sure we are not losing speed though. See #1069. There are a few others due to how the mocked netcdf Dataset is built. I've been unable to get rid of those. Investigating more... But you can see them in action when you call |
@jcermauwedu I never experienced a segfault like that but do you mind testing against #1069 to see if that solves your problem? |
A stress test yielded no more segfaults. If another one appears, we will let you know. Using the latest commit, the output is squeaky clean. Thanks @benjwadams @ocefpaf
|
Most tests apparently pass. With python 3.11.9, there are these floating around.
Intermittently, I can trigger a segfault...
The text was updated successfully, but these errors were encountered: