You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Only about 3 out of 10 runs for the sanitizer actually succeed, most others die with a segfault. I believe this has started when we turned on running the sanitizer for examples.
I have investigated it a bit.
The problem is occurred after running this pipeline with introduced memory leak. #1286
Then it creates cache of the GHA and when it's used segfaults happens during installation. So, cleaning of the cache for GHA fix this problem. I guess we should just dissable caching for this step. Not sure how caching is working with the steps which use docker containers.
What happens, and what did you expect instead?
Only about 3 out of 10 runs for the sanitizer actually succeed, most others die with a segfault. I believe this has started when we turned on running the sanitizer for examples.
To reproduce
https://github.com/igraph/rigraph/actions/workflows/build-and-check.yml
System information
No response
The text was updated successfully, but these errors were encountered: