Skip to content
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

Detecting CMOR seg faults #20

Open
paolap opened this issue Jul 28, 2023 · 0 comments
Open

Detecting CMOR seg faults #20

paolap opened this issue Jul 28, 2023 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@paolap
Copy link
Collaborator

paolap commented Jul 28, 2023

Occasionally CMOR will produce a set fault (see their GitHub for examples of when this happens). As the segfault signal can't be detected in a try/except or other usual ways as it happens in a different package (i.e. CMOR) nothing get passed to the the working process and from multiprocessing Pool and this just goes on indefinitely until the PBS jobs reaches walltime.
I'm trying to move to concurrent to test these approaches:
https://stackoverflow.com/questions/70356876/python-multiprocessing-skip-child-segfault
so far no luck, but I haven't try yet to introduce a timeout

@paolap paolap self-assigned this Jul 28, 2023
@paolap paolap added the bug Something isn't working label Jul 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant